Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

best.py or bestpy #2

Closed
gustavwilliam opened this issue Nov 22, 2020 · 2 comments
Closed

best.py or bestpy #2

gustavwilliam opened this issue Nov 22, 2020 · 2 comments
Labels
discussion

Comments

@gustavwilliam
Copy link
Owner

Should we call this best.py or bestpy? They both have their pros and cons.

@fisher60 what do you think?
@fisher60
Copy link
Collaborator

Hmmmm, I feel that best.py is a bit arrogant, but I certainly do not want or files to be bestpy.py.

I am leaning towards best.py, but I also despise when packages have a different import than their package name/pip install, so we would need to ensure we can get the name.

@gustavwilliam
Copy link
Owner Author

True. Since best is already taken on PyPi, bestpy may actually be our best option. Let's go with that. At least for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@fisher60 @gustavwilliam