3 ms·
"Not sure I understands why you're having so much trouble" ... proceeds to explain a procedure that involves understanding various moving parts, including virtu
by emmanueloga_ 6y ago
"Not sure I understands why you're having so much trouble" ... proceeds to explain a procedure that involves understanding various moving parts, including virtualenvs, pip, setuptools, wheel, etc...
Even if I'm not gonna get deep into python, I like to feel like I understand what's going on. With python it just involves a lot more effort than with other ecosystems, even if you think that these things are easy to learn.
Compare with ruby: `gem install the-gem`. Done. No "virtual envs", no plethora of similar but different tools to do slightly the same thing / whatever, no preconditions, no step by step procedures. Simplicity is important!
- ElliotH 6y agoMy experience of Ruby, which is admittedly a few years old, is that people did use multiple Ruby environments through e.g rbenv to manage different sets of gem versions, which is what "virtual envs" are the equivalent of. Now, I do agree the Python tooling situation is kind of a mess, but there you can still do: "pip install the-package" And you're just as good, all the other tools are when you're trying to do stuff harder like: - Maintain multiple development environments - Publish new packages - Build binary packages - Handle Windows I think on Ruby you need tools beyond "gem install" to do those as well. The point is how we achieve simplicity while keeping the ability to do those things.
- helgie 6y agoYou can just do 'pip install the-package' in python if you aren't using a virtual environment. Ruby does have the equivalent of virtual environments, using RVM or rbenv (similar but different tools), to solve the same problems as in Python.