supervisor is still marked as non-support to Python 3 on https://python3wos.appspot.com

[dalguji]

I see supervisor is now happily supporting Python 3 but it still appears marked as non-support to Python 3 on https://python3wos.appspot.com and http://py3readiness.org

py3readiness.org mentions that it uses https://github.com/brettcannon/caniusepython3 to check availability of the package. We can see the online check for supervisor here: https://caniusepython3.com/project/supervisor

I am not sure why the online checker says supervisor has 1 blocker for python 3 port.

[mnaberez]

The master branch has work-in-progress support for Python 3. If Python 3 support is important to you and you're comfortable running the code on master, we'd appreciate if you could test it and report any issues that you find.

There still a few things that need to be addressed before a stable release to PyPI can be made (e.g. see this comment about an issue that @mcdonc is working on). We'd like to make a PyPI release, but aren't comfortable releasing it at this time because it may have bugs and performance regressions that also impact Python 2 users.

[flypenguin]

then please make a supervisor3 release, or something - the first SO question is almost 3 years old ...

[mnaberez]

Issues tagged python 3 need to be resolved before any kind of release could be made.

[flypenguin]

that was not my suggestion :)

[mnaberez]

I read your comment. I replied that the issues need to be resolved before any kind of release can be made (it could be called "supervisor3" like you suggested, or the existing package name, or whatever). This software does not work reliably on Python 3 yet. It doesn't matter what the package is called. I'm not willing to release a version that I know is going to blow up and take down some production website. When the Python 3 issues are actually resolved, I would be happy to make a release.

[nueverest]

Is there a projected release date for the python 3 support?

[johnrickman]

Bump

[loganbest]

bump

[yonatann]

bump

[ndmeiri]

Bump

[ahaerpfer]

bump

[viennadd]

bump

[jcyrss]

bump

[j-walker23]

Is there anywhere we can see a release schedule?

[infintesimal]

bump
I appreciate the hard efforts of the maintainers and would love to see them cut a tag of 4.0.0.

I have installed via pip from github master. I checked the github site and I don't see any open issues with the python3 label so would love to know what gates still need to be cleared before 4.0.0 can be tagged.

For what it's worth, I don't really think there is ever any defect free software. If some big production site blows up on py3 they will have the resources to revert or rollback. And any large scale site would be sure to test and stage this (they have their own risk management strategies and approaches). So if the vast majority of known issues are done, why not just put it out there with caveat emptor and new reports can trickle in.

[samuelhwilliams]

^ please

[bartmika]

Bump

[matticus]

Also interested. Happy to help if there is some outstanding work needed to bring this to stable.