News for hackers. Stuff that matters.

A comment on Perl 11. Parent comment

Re:Perl 11 by SmirkingRevenge on Wednesday October 24, 2018 @01:51AM (#18290016)
> NPM might suck for various reasons but at least all deps are installed local to each project. I'm sure there are secret incantations for doing the same in perl and python but by default most stuff I download requires global libraries to be installed

No magic required in Python at all for this. Just use virtualenv from your project directory (don't bother with vitrualenvwrapper).

    $ virtualenv venv; . ./venv/bin/activate
[ Parent | on HN ]
Re:Perl 11 by tokyodude on Wednesday October 24, 2018 @09:23AM (#18292150)
IMO it *is" magic because it's not the default.

with npm I have to go through special effort to get anything to install globally. With both python and perl I've read countless books and websites over the last 20 years and never once ran into that incantation. They all just say type

    install Chocolate::Belgian
or

    cpan Chocolate::Belgian
or

    python -m pip install SomePackage
etc..
[ Parent | on HN ]
Re:Perl 11 by doteka on Wednesday October 24, 2018 @10:13AM (#18292561)
That's just intellectually dishonest, it's part of the official language tutorial...

https://docs.python.org/3/tutorial/venv.html

[ Parent | on HN ]
Re:Perl 11 by tokyodude on Wednesday October 24, 2018 @12:59PM (#18294212)
Chapter 12!
[ Parent | on HN ]
Re:Perl 11 by tech2 on Thursday October 25, 2018 @09:10AM (#18300588)
Likewise don't bother with `activate`, just use the tools from the virtualenv directly `venv/bin/pip`, `venv/bin/python` etc.
[ Parent | on HN ]