263 karma · joined April 17, 2015
> ...
> We recommend that OEMs, Cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions on the below platforms, as they may introduce higher than expected reboots and other unpredictable system behavior.
Is that you bunnie? Or someone from Boston who was inspired by bunnie?
(bunnie = https://www.bunniestudios.com/ reverse engineer too, graduate from MIT)
In Fedora we have (most recent change in packaging guidelines):
Source rpm: python-foo which generates binary rpms: python2-foo and python3-foo where python2-foo has virtual provides for python-foo, once Python3 will become THE default python by the upstream merits we will change python-foo provides to python3-foo package.
python-sphinx and python2-sphinx
From this I conclude that python-sphinx is python3 version of sphinx right? Do you think that's sane (from user experience point of view) assuming that /usr/bin/python should point to python2? https://www.python.org/dev/peps/pep-0394/
See in __call__ method http://sourcefoundry.org/hack/assets/img/mockup/python-sourc...
http://copr-fe.cloud.fedoraproject.org/coprs/rkuska/passpie/
Currently we are waiting for a last few packages to be ported (anaconda is already running on python3 and ready for Fedora 23 release). Ironically the hardest part isn't porting (we've sent a huge amount of patches to upstream projects) but getting upstreams to accept the python3 as supported interpreter ("what is this python3 thing?" yes, this is a real quote).
I am happy to see a new distros joinning a party, gl!