pipenv

> The lack of Python requirements.txt support is a bit odd I hope they go with Pipfile/Pipfile.lock [0] and pipenv [1] rigth away! [0] https://github.com/pypa/pipfile [1] https://github.com/kennethreitz/pipenv

Also for python `pipenv check`[0] to do security checks (obviously for known vulnerabilities) if you use pipenv[1] to manage dependencies. [0] https://docs.pipenv.org/advanced.html#detection-of-security-... [1] https://github.com/kennethreitz/pipenv

and Pipfile - which is what i've switched to in recent projects, example[0] Altho you can write to one of the other formats or read from it - you'd have to tell the scanner what the true build source is [0] https://github.com/kennethreitz/pipenv/blob/master/Pipfile

pipenv[1] and other GitHub repos have a little badge in the REAMDE.md entitled "say thanks", which takes you to a simple form [2] where you can say thanks. I thought it was a cool idea. [1] - https://github.com/kennethreitz/pipenv [2] - https://saythanks.io

Maybe, the project as a whole seems to be under a year old and is under very active development. Probably 7.0.0 or 3.2.9, where current version is 8.2.6: https://github.com/kennethreitz/pipenv/blob/master/HISTORY.t... Also, I guess --python 3.4 would be the preferred way to do it, seems to work with either versions or executables.

Twine[0] is the tool I've been using for PyPI archive management and Pipenv[1] is looking promising as the next iteration of pip. Twine makes the packaging process _slightly_ easier, although setuptools is still a bit of a pain. Pipenv handles a lot of project cruft for you: setting up a virtualenv, distinguishing dev and prod packages, locking them down and deterministic building. [0]: https://github.com/pypa/twine [1]: https://github.com/kennethreitz/pipenv

Have them try Pipenv! https://github.com/kennethreitz/pipenv While virtualenv management isn't that difficult, Pipenv is VERY intuitive.

Looks like it does a bit too much. I like pipenv https://github.com/kennethreitz/pipenv

> Yarn may well be better than npm, in fact, as far as I can tell it is, but, frankly, npm works well and I'm tired of switching js dependencies, especially really core dependencies like a package manager... Yarn still uses your package.json. I think it will definitely win out over directly using npm since it is better in a couple of ways and, from a user perspective, is just a thin wrapper around the things you're already used to doing. Ways my workflow has changed: npm install . -> yarn npm save --dev pkg -> yarn add --dev pkg npm save pkg -> yarn add pkg npm run command -> yarn run command If you start using it and dislike it, just npm uninstall -g yarn, rm the yarn.lock file and bam, you've still got a normal npm dependency management setup. > If yarn were available for python, I'd switch to it today Project worth keeping your eye on: