Log file Viewer

[14:10:04] <folon> Hi, how can I install packages by pip but in an isolated environment ? (I don't want install packages system wide)

[14:11:23] <toad_polo> folon: The traditional way to do it is with `virtualenv`.

[14:11:32] <toad_polo> Or on Python 3 there's the built-in `venv`.

[14:11:49] <toad_polo> You can also use `pip install --user` to install just for your user, that's not isolated, though.

[14:12:53] <folon> toad_polo: ok, I'll use virtualenv

[14:13:45] <toad_polo> 👍

[14:34:09] <GothAlice> <3 venv

[14:34:21] <GothAlice> folon: Do you use Zsh, by chance?

[14:56:41] <folon> GothAlice: I am sorry if I haven't replayed soon, I've seen your answer just now. Anyway no

[14:57:39] <folon> and I can't use virtualenv because I use openbsd that cannot permit w^x binary outsite /usr

[14:57:49] <folon> then I just installed what I need system wide

[15:00:09] <GothAlice> folon: Given the executable doesn’t need to be writeable after population of the environment, chmod -w that, problem solved, no?

[15:00:52] <GothAlice> (E.g. instead of trying to resist the sensible security precaution, understand the intent—allowing writeable executable code is BAD—and fix the actual problem, writeable code.)

[15:14:28] <folon> it doesn't execute... it's executable but I can't execute. It's not a writeble problem

[15:19:09] <GothAlice> “cannot permit W^X binary outside /usr” — I misread as W for writeable, but this means world. Indeed, the fix is still trivial: chmod u+x w-x it. You need to be able to execute it, but no other theoretical person on your machine does.

[15:22:05] <folon> GothAlice: it's a kernel feature and a slice mount point option

[15:23:08] <folon> myblahblahslie /usr/local ffs rw,softdep,noatime,wxallowed,nodev 1 2

[15:23:59] <folon> wxallowes means I can execute, outside /usr/local you cannot execute anything.. even if u are root and with right permission... you cannot

[15:24:36] <ngoldbaum> seems like it would be painful to do development on openbsd

[15:40:26] <Xelnor> folon: you could create your virtualenv inside /usr/local though :)

[15:48:10] <GothAlice> As a note, I often have venv directories divorced from my project code. I just symlink the actual venv path into $PROJECT_ROOT/.venv and poof, it’s all good.

[15:48:21] <GothAlice> E.g. /usr/local/container/marrow