Naming Conventions? #13
Replies: 4 comments
-
@desaibhargav @smwwood @justinnwood @mchivuku I'd love to hear your thoughts. |
Beta Was this translation helpful? Give feedback.
-
I've created a branch for this here: https://github.com/buildingamind/NewbornEmbodiedTuringTest/tree/name-changes Also, I was thinking of doing the following: |
Beta Was this translation helpful? Give feedback.
-
Completed in #20 |
Beta Was this translation helpful? Give feedback.
-
As per discussion, we are going with |
Beta Was this translation helpful? Give feedback.
-
It seems like our naming conventions are all over the place. We install
nett-benchmarks
. We importnetts
. And our repo isNewbornEmbodiedTuringTest
which abbreviates toNETT
notNETTS
and not evenNETTs
because it's only one test.I noticed that
nett
is available to grab on PyPI. Personally, I think it would make the most sense to just switch over tonett
and importnett
. That would simplify things, but if it's too difficult to change what name we are registered under, maybe we importnett_benchmarks
ornettBenchmarks
?Seems like we have the following options:
nett-benchmarks
, Import*:nett
, Repo:NewbornEmbodiedTuringTest
netts-benchmarks
, Import*:netts_benchmarks
, Repo*:NewbornEmbodiedTuringTests
orNewbornEmbodiedTuringTests-Benchmarks
netts.nett
becomingnetts_benchmarks.nett
netts-benchmarks
, Import:netts
, Repo*:NewbornEmbodiedTuringTests
orNewbornEmbodiedTuringTests-Benchmarks
nett
, Import*:nett
, Repo:NewbornEmbodiedTuringTest
nett.NETT
would exist (a name change of NETT could fix this but it is also fine as is)pip install netts
which is a different package and vice-versanett-benchmarks
Beta Was this translation helpful? Give feedback.
All reactions