When the Ruby team makes changes the attitude is generally 'deal with it'. Sure they still do point releases on older versions but only for security issues AFAIK.
Python moves forward it just does a poor job of dragging everyone with it.
When the Ruby team makes changes the attitude is generally 'deal with it'. Sure they still do point releases on older versions but only for security issues AFAIK.
Python moves forward it just does a poor job of dragging everyone with it.
However they complement this attitude by being a lot better at working with big 3rd party library developers and making sure they are on board. To the best of knowledge there has never been a Ruby release that was incompatible with RoR for any period of time. Compare to Python that jumped to python 3 without either numpy or Django on board.
- Pythonz
- Conda
- Pew (disclaimer: I'm the author)
- Virtualenvwrapper
- Pyenv
Etc.
If you argue that people might not move to the latest and greatest as soon as possible due to the fact that people don't build their own interpreter, I can definitely agree with it: python users seem to truly prefer the python version that already comes pre-installed with their linux distribution
Definitely. It's not that Python doesn't have the tools to switch between versions, but it's not as prevalent as is in the Ruby community. Most Python users will start their program with shebangs like
#!/usr/bin/env python
or if they want Python 3+ #!/usr/bin/env python3
while not necessarily using tools like virtualenv and virtualenvwrapper.I feel like shebangs are not as commonly used in Ruby, instead you use tools and your Gemfile to specify Ruby version.
Maybe it's just the grass is always greener.