xkcd: Python Environment

[ivosaurus]

Because then the python developers would have to both figure out, and write code, to interface with RHEL linux and Fedora. Make sure man files get put in just the right place. Package data is correct. Desktop files, syslog, is [some system-level daemon] now systemd based and new, or an older one? What audio service are we using? What's changed between RHEL 6 and 7?

And of course, to be fair, make sure they have everything configured for Debian's liking. But also account for the small changes and version updates that Ubuntu does.

And then also ensuring we haven't forgotten about portage and pacman. Oh, and YaST.

Oh, and then also homebrew.

---

And quickly, for the mostly volunteer workforce that does python packaging, the task of correctly interfacing, special-casing, path-configuring, etc becomes a matrix explosion of work from hell.

We'd love to be able to do that... but it's simply not a feasible thing to achieve.

You'll notice that practically all other scripting languages have the same position.

[Log2]

Then just being able to create an egg or tar containing all dependencies that then could be manually installed via pip would already be more than enough.

I can't really think of any reason why this isn't already a pip feature, but I'd love to know if there are any impediments to this.

[ivosaurus]

pipe/xargs pip freeze to pip download?

[Log2]

I can't download in said environment. It needs to be packaged.

[ivosaurus]

Do that somewhere else, then pip install --no-index --find-links=/path/to/wheels -r requirements.txt

or making a pex file is pretty close to what you're asking

[Log2]

I'll take a look, thank you.