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
{{ message }}
This repository has been archived by the owner on Oct 8, 2024. It is now read-only.
Sorry to be that guy who tries to get you to change your preferred programming tools.
pipenv is by the same guy who made the Python Requests library. It's a dependency management and project build tool, in many ways similar to Cargo for Rust.
The main benefit off the top of my head to using pipenv over venv is that getting set up is as simple as pipenv install (think cargo install) and running is as easy as pipenv run python <main.py> (think cargo run), and the run targets can be configured so that pipenv run mytask works without specifying the script file path.
I'd imagine with the custom run task scripting you could define a configuration that automatically runs pylint and mypy for you.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sorry to be that guy who tries to get you to change your preferred programming tools.
pipenv
is by the same guy who made the Python Requests library. It's a dependency management and project build tool, in many ways similar to Cargo for Rust.The main benefit off the top of my head to using
pipenv
overvenv
is that getting set up is as simple aspipenv install
(thinkcargo install
) and running is as easy aspipenv run python <main.py>
(thinkcargo run
), and the run targets can be configured so thatpipenv run mytask
works without specifying the script file path.I'd imagine with the custom run task scripting you could define a configuration that automatically runs
pylint
andmypy
for you.The text was updated successfully, but these errors were encountered: