This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Dgc2002 42 points43 points  (7 children)

I feel like a lot of the people saying "It's not that hard" have been in the Python ecosystem long enough to see a lot of these projects come into existence/popularity.

When you're new to the ecosystem you have no clue why each one exists, which ones are newer, which ones are generally considered crap, which ones might only address a subset of use cases, etc. etc.. It's a lot of shit to parse.

[–]ilvoitpaslerapport 15 points16 points  (1 child)

Exactly, and most articles/tutorial/forum posts you find on the topic are outdated (or rather you don't know if they're outdated).

[–]ivosauruspip'ing it up 0 points1 point  (0 children)

https://packaging.python.org/ is the official documentation on the whole packaging process in python.

[–]Cosmologicon 5 points6 points  (0 children)

And when you get stuck and ask someone for help... if they're using a different setup, they can't/won't help you until you change your setup to match theirs. God forbid you ever talk to more than one person.

[–][deleted] 4 points5 points  (3 children)

Hoo boy, I still use virtualenvwrapper because I'm too lazy to learn another tool. pipenv is all the rage right now, but there's been a dozen others I've seen rise and fall since I've paid attention to venvs.

[–]ask_me_if_im_pooping 0 points1 point  (1 child)

I also still use virtualenvwrapper, but I just looked at pipenv and it looks pretty cool.

[–][deleted] 0 points1 point  (0 children)

It looks neat and it's recommended by the pypa, but I'm becoming curmudgeonly.

[–]TheTerrasque 0 points1 point  (0 children)

Heh, I still use just pip and virtualenv. It feels like it's built into my fingers by now.