News for hackers. Stuff that matters.

A comment on Remacs – A community-driven port of Emacs to Rust. Parent comment

Re:Remacs – A community-driven port of Emacs to Rust by baq on Sunday July 16, 2017 @03:29PM (#14783731)
with python the rule should to be to run every deployment at least in its own venv.
[ Parent | on HN ]
Re:Remacs – A community-driven port of Emacs to Rust by Symbiote on Sunday July 16, 2017 @04:01PM (#14783858)
That's not so practical if the application is a text editor, or some other administration tool (debugging, statistics etc).
[ Parent | on HN ]
Re:Remacs – A community-driven port of Emacs to Rust by tonyarkles on Sunday July 16, 2017 @09:35PM (#14785081)
I recently came across this: https://github.com/spotify/dh-virtualenv

For a system utility, you can still use virtualenvs. The launcher script just needs to use a shebang like:

    #!/usr/share/spiffyapp/venv/bin/python
[ Parent | on HN ]
Re:Remacs – A community-driven port of Emacs to Rust by nine_k on Sunday July 16, 2017 @08:28PM (#14784837)
My rule of thumb is to never install anything into system Python by pip, etc. If it's not an OS package, it belongs to a virtualenv.
[ Parent | on HN ]
Re:Remacs – A community-driven port of Emacs to Rust by fiddlerwoaroof on Sunday July 16, 2017 @10:35PM (#14785287)
I more or less have this rule, except I generally will use the --user flag to install things on a per-user basis if it's not being installed for a particular project.
[ Parent | on HN ]