You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have small doubts about optimake being potentially mixed up with optimade in the following contexts:
In oral communication. e.g. when someone says "we use optimake to ...", someone, who might not be aware of the package, might assume they meant "we use optimade to ...".
in various contexts related to the python package (e.g. on exploring pypi.org, looking at pip freeze, seeing pip install optimake/optimade) it might cause confusion.
On the other hand optimade_maker shouldn't have this problems.
Regarding the CLI tool, these points don't really apply directly (e.g. there is no optimade executable), so perhaps that is fine to keep as optimake. And i think it's fairly common to use a different name than the package name for this.
This repo will most likely only contain a single python package (currently named
optimake
).I recently also published it to pypi: https://pypi.org/project/optimake/
I have small doubts about
optimake
being potentially mixed up withoptimade
in the following contexts:pip freeze
, seeingpip install optimake/optimade
) it might cause confusion.On the other hand
optimade_maker
shouldn't have this problems.Regarding the CLI tool, these points don't really apply directly (e.g. there is no
optimade
executable), so perhaps that is fine to keep asoptimake
. And i think it's fairly common to use a different name than the package name for this.@ml-evs what do you think?
The text was updated successfully, but these errors were encountered: