-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
Removing legacy build system #36
base: develop
Are you sure you want to change the base?
Conversation
@@ -7,7 +7,6 @@ __pycache__/ | |||
*.so | |||
|
|||
# Distribution / packaging | |||
Pipfile.lock |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We generally don't want to include Pipfile.lock for libraries because that ties us into dependencies for a specific Python version and potential contributors might not have the same version as us, potentially creating issues for them (and likely making most PRs play a game of cat-and-mouse game of different people re-locking on different versions)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally don't want to include lock files in gitignore? Or don't want to include them in git?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I see how that was ambiguous. We don't want to include it in version control for projects that aren't pinned to a specific Python version
No description provided.