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.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
It seems like our naming conventions are all over the place. We install
nett-benchmarks. We importnetts. And our repo isNewbornEmbodiedTuringTestwhich abbreviates toNETTnotNETTSand not evenNETTsbecause it's only one test.I noticed that
nettis available to grab on PyPI. Personally, I think it would make the most sense to just switch over tonettand importnett. That would simplify things, but if it's too difficult to change what name we are registered under, maybe we importnett_benchmarksornettBenchmarks?Seems like we have the following options:
nett-benchmarks, Import*:nett, Repo:NewbornEmbodiedTuringTestnetts-benchmarks, Import*:netts_benchmarks, Repo*:NewbornEmbodiedTuringTestsorNewbornEmbodiedTuringTests-Benchmarksnetts.nettbecomingnetts_benchmarks.nettnetts-benchmarks, Import:netts, Repo*:NewbornEmbodiedTuringTestsorNewbornEmbodiedTuringTests-Benchmarksnett, Import*:nett, Repo:NewbornEmbodiedTuringTestnett.NETTwould exist (a name change of NETT could fix this but it is also fine as is)pip install nettswhich is a different package and vice-versanett-benchmarksBeta Was this translation helpful? Give feedback.
All reactions