5 ms·
Clicking around, those that don't seem to be: 1. Obsolete. Either explicitly so (e.g. Google API) or abandoned, without even a minor/patch release (initools,
by sago 9y ago
Clicking around, those that don't seem to be:
1. Obsolete. Either explicitly so (e.g. Google API) or abandoned, without even a minor/patch release (initools, 2010) or in some cases a code commit (e.g. pathtools, 2012) for five years or more. I suspect that they will never be Py3, the community will just move on to alternatives.
2. Working hard to bring support (e.g. ansible).
3. Part of the graphite ecosystem. If the base library won't change, none of its ecosystem will.
4. Not on public version control / issue tracking, so who knows (e.g. supervisord)
- ams6110 9y agoLack of commit activity doesn't necessarily mean a package is obsolete. A small set of well defined functionality can be "done" at some point and need no further changes.
- sago 9y agoMy choice of word was unnecessarily pejorative. I agree. Though I would say that it's the stretch to say it might 'need no further changes' if it doesn't work with the latest version of python.
- crdoconnor 9y agoAll software rots because even if the functionality never needs to change, the world (and the APIs) around it will. Some code just rots slower than others.
- finnn 9y agoA brief look around the supervisor site indicates that they have public version control and issue tracking on their github page[0] and that they have a merged PR[1] to add python 3 testing (which appears to be passing). [0] https://github.com/Supervisor/supervisor https://github.com/Supervisor/supervisor [1] https://github.com/Supervisor/supervisor/pull/901 https://github.com/Supervisor/supervisor/pull/901
- piquadrat 9y agoAccording to their README[1], supervisor does not yet work correctly on Python 3 and has a list of issues [2]. [1] https://github.com/Supervisor/supervisor/blob/master/README.rst https://github.com/Supervisor/supervisor/blob/master/README.... [2] https://github.com/Supervisor/supervisor/labels/python%203 https://github.com/Supervisor/supervisor/labels/python%203
- sago 9y agoThank you. I wonder why they don't list this in their setup.py
- collinmanderson 9y agoThey do. I wonder why it's not green. https://github.com/Supervisor/supervisor/blob/master/setup.py#L59-L64 https://github.com/Supervisor/supervisor/blob/master/setup.p...
- collinmanderson 9y agoOhh, they just haven't released it to pypi yet.
- sago 9y agoI meant the repo and bug tracker, which is can we listed in setup.py and is picked up by pypi.
- collinmanderson 9y agoThe repo has Python 3 listed in setup.py. Are you saying it isn't? (It's not getting picked up by pypi because they haven't made a release with the trove classifier yet.)
- sago 9y agoNo, setup.py doesn't list the repo and bug tracker, so pypi doesn't list the repo and bug tracker either.
- djsumdog 9y agoHuh. I know if I have a server that only has python3, Ansible can configure that server with only the python3 interpreter available. So Ansible can use python3 on the box it's configuring, but not the host it's running from?
- y4mi 9y agoyes, its the ansible binary that needs python2. there is experimental python3 support since 2.2 though.
- guhcampos 9y agoI believe they just haven't officially defined Ansible as Python 3 compliant because there are still open issues in Github related to Python 2. I have been using Ansible exclusively with Python 3 for over a year and only stumbled into incompatible code once, a simple case of string VS bytes literals that got quickly fixed.
- y4mi 9y agoso you're executing ansible with: python3 /usr/bin/ansible $cmd if you're using plain `ansible` from the repos or pip, you're using python2. /edit: there is actually a source for that, go figure: http://docs.ansible.com/ansible/latest/python_3_support.html http://docs.ansible.com/ansible/latest/python_3_support.html
- odonnellryan 9y agoSupervisord isn't open source? What
- adamtulinius 9y agoOpen source doesn't mean the source must be publicly available for everyone to read. :)
- feikname 9y agoThat's exactly what I thought open source meant. How can a source be open if not everyone can read it? I didn't get your comment.
- ZenoArrow 9y agoOpen source can mean that the source is available on request, or is available after purchasing a licence. It doesn't have to be publicly available to be open source, though in practice it pretty much always is.
- odonnellryan 9y agoTrue :) I've just come to think Open Source == FOSS
- collinmanderson 9y agoEven with the GPL, the source doesn't need to be publicly available for everyone to read. Only paying customers are guaranteed the right to the code. (Some car makers have GPL software and only give out the source code to verified car owners.)
- nerdwaller 9y agoIf you do need supervisord, a (from my experience) suitable alternative is circusd. Though I’ve since moved to having either the operating system’s process manager (usually systemd anymore) or docker become my process manager.
- Too 9y ago5. Has other equally or more cable alternatives in python3. Eg there's no reason to use python-ldap when you have ldap3.
- git-pull 9y agoIn addition, Fabric doesn't support Python 3. The feedback I've gotten back on when Python 3 will be supported and how much of the legacy fabric API's will be supported is even more limited. There is a fork with Python 3 support: https://github.com/mathiasertl/fabric/ https://github.com/mathiasertl/fabric/ If you use fabtools, I maintain a fork of it for fabric3: https://github.com/develtech/fabtools/tree/fabric3 https://github.com/develtech/fabtools/tree/fabric3
- msl09 9y agoI use your fork, thank you for your work!
- deleted 9y ago[deleted]
- collinmanderson 9y agoYeah, the fabric3 fork works really well. Also, the fabric author has been making a lot of progress on Fabric 2, which works on Python 3. https://github.com/fabric/fabric/tree/v2 https://github.com/fabric/fabric/tree/v2
- deleted 9y ago[deleted]