-
Notifications
You must be signed in to change notification settings - Fork 145
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
Consider scripts section similar to npm package.json #62
Comments
Wouldn't this be better in something like |
I don't know if working with |
As of now, this functionality is provided by non-pip tools. Pipfile is meant to be a replacement for the requirements.txt format. It would definitely be great to have something to automatically run the tests and all. It's just not something for Pipfile to handle. This will be provided as a part of pyproject.toml, so that build tools can use it. Pipfile is for handling and managing dependencies. |
Yea, this is something that would go inside of |
Originally this issue was filed to the |
Adding an official section to |
If I understand correctly there is no such tool yet? |
There are no such tools that I know of. Currently, the details of the file are still being worked on. PEP 518 is a start to adding proper declarative build information and build system determination. As I see it, the rest will be specified in the near future. |
Hi, thanks for yet another awesome tool!
I wander if there is any plans to add commands abbreviations for example in scripts section.
So instead of typing each time pipenv run python -m unittest discover it will be enough to run pipenv test (or maybe pipenv apply test) if we have this in the Pipfile:
Moved from https://github.com/kennethreitz/pipenv/issues/153
The text was updated successfully, but these errors were encountered: