[opensuse-python] Please do not abuse your approval rights on d:l:p [Was: Re: Python 2 EOL]
Happy New Year everybody. Unfortunately, with the upcoming death of Python 2 packages in Factory, we have got into rather unpleasant situation: On 2019-11-21, 21:46 GMT, Todd Rme wrote:
Python 2 EOL is happening in a little under a month and a half. However, I am unclear what our plans are. Is there any specific set of actions we are going to take in response to this? Is there a timeline?
Hi, Todd, I understand that the communication about this was not optimal (there were some problems with suse.com SMTP server not sending to this list), but still I insist that changes of this magnitude should be properly communicated beforehand with me, Steve, or Tomáš. Please, also follow the current discussion on https://lists.opensuse.org/opensuse-factory/2020-01/msg00095.html this. Yesterday (or starting a day before yesterday) you have submitted and approved himself over hundred of submit requests to various Python-related packages. You did so without consulting with anybody and we now have to recover OBS from this avalanche. When planning such massive change as Python 2 EOL there are more considerations than what is just obvious to you from your side. See for example your request https://build.opensuse.org/request/show/762506 , which we need to reapply as https://build.opensuse.org/request/show/762857 instead. Specifically, do not add more skip_python2 definitions, we will do it on the project/distro level later, no need to do it for each package individually. Right now, the focus should stay on removing the leaf packages (not required by anything else), and we can continue later to more core ones. However, this is not the first time we have problems to communicate with you. I completely appreciate huge amount of work you do for openSUSE, but these situations when we need to recover the distro from your mass submissions (self-approved by you) make me believe that if something does not change, we will need to let you just file request and we will have to check them ourselves before their approval. Please, do communicate such massive changes here, on IRC, or on Trello beforehand. Best and thank you again for all you do for openSUSE, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Courage is resistance of fear, mastery of fear, not absence of fear.
Am Freitag, 10. Januar 2020, 17:52:43 CET schrieb Matěj Cepl: Hi Matej,
Happy New Year everybody. Unfortunately, with the upcoming death of Python 2 packages in Factory, we have got into rather unpleasant situation:
Can you summarize where the current python 2.x policy is documented? I was actually also dropping python 2.x stuff unconditionally (at least for things only building for SLE15+ anyway) Thanks, Dirk -- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org
On 2020-01-13, 12:33 GMT, you wrote:
Can you summarize where the current python 2.x policy is documented?
I was actually also dropping python 2.x stuff unconditionally (at least for things only building for SLE15+ anyway)
1. Do NOT just add skip_python2 — we will remove python2 in the project configuration eventually, so it is unnecessary 2. Do NOT remove python2 constructs — there is still python2 in Leap 15 (and SLE) and we from time to time want to use d:l:p* packages for both. We plan to wrap them with just suse_version <= 1500 after we would've killed all the leafs that are atm flying off. 3. DO keep using single spec macros! We are in no way planning to abandon it and use it for future alternative pythons (pypy, python3.* coinstall). 4. DO remove python2-only packages from Factory. There are lists of packages using python2-setuptools (https://trello.com/c/XaVFZE8n) and python2-devel (https://trello.com/c/v4XyXC4O) at the Python Trello (https://trello.com/b/WsskhdXA/opensuse-python) and you are very welcome to: - investigate the situation (couldn’t the package be moved to single-spec py3-including state? perhaps after upgrade?), - with priority work on d:l:p itself (or if you are especially passionate about some subproject, feel free to go for it), and move from leafs to the trunk in the dependency tree (don’t start by killing python-unittest2 as much as I would like it DIE SOON; EAT FLAMING DEATH!) - drop all the leaf packages that are not py3 compatible - conditionalize optional python2 support for < TW or drop the py2 support depending on the package (rule of thumb, if nobody bothered to touch the pkg upstream >1year then it looks like it will never be backported) - move py2->py3 packages where applicable (like the darn fail2ban we had under py2 until now). - someone internal needs to talk with cloud ppl to ask for removal of all the openstack stuff that pulls py2 directly (already gave headsup to Nanuk) - specifically, please do not use %python3_only, as we wanna switch to the multipython even on python3 and this would kill it. https://trello.com/c/VWZdVunC 5. Changes in macros and switching off python2 on macro/project level will be done when the leaf packages are gone. Best, Matěj -- https://matej.ceplovi.cz/blog/, Jabber: mcepl@ceplovi.cz GPG Finger: 3C76 A027 CA45 AD70 98B5 BC1D 7920 5802 880B C9D8 Q: Is vi an easy editor to learn, is it intuitive? A: Yes, some of us think so. But most people think that we are crazy. -- vi FAQ
On Mon, Jan 13, 2020 at 8:37 AM Matěj Cepl
On 2020-01-13, 12:33 GMT, you wrote:
Can you summarize where the current python 2.x policy is documented?
I was actually also dropping python 2.x stuff unconditionally (at least for things only building for SLE15+ anyway)
1. Do NOT just add skip_python2 — we will remove python2 in the project configuration eventually, so it is unnecessary
What about packages that have dropped python2 themselves? nbformat 5 came out and it drops python2 support. -- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org
On Wed, Jan 15, 2020 at 10:11 AM Todd Rme
On Mon, Jan 13, 2020 at 8:37 AM Matěj Cepl
wrote: On 2020-01-13, 12:33 GMT, you wrote:
Can you summarize where the current python 2.x policy is documented?
I was actually also dropping python 2.x stuff unconditionally (at least for things only building for SLE15+ anyway)
1. Do NOT just add skip_python2 — we will remove python2 in the project configuration eventually, so it is unnecessary
What about packages that have dropped python2 themselves? nbformat 5 came out and it drops python2 support.
prompt_toolkit 3, which is required by the latest ipython, also drops python2 support -- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org
On Wed, Jan 15, 2020 at 10:46 AM Todd Rme
On Wed, Jan 15, 2020 at 10:11 AM Todd Rme
wrote: On Mon, Jan 13, 2020 at 8:37 AM Matěj Cepl
wrote: On 2020-01-13, 12:33 GMT, you wrote:
Can you summarize where the current python 2.x policy is documented?
I was actually also dropping python 2.x stuff unconditionally (at least for things only building for SLE15+ anyway)
1. Do NOT just add skip_python2 — we will remove python2 in the project configuration eventually, so it is unnecessary
What about packages that have dropped python2 themselves? nbformat 5 came out and it drops python2 support.
prompt_toolkit 3, which is required by the latest ipython, also drops python2 support
Edit, nevermind, the changelog was (arguably) misleading. Prompt toolkit 3 is not required, only supported. It is python3 only, though. -- To unsubscribe, e-mail: opensuse-python+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-python+owner@opensuse.org
participants (3)
-
Dirk Mueller
-
Matěj Cepl
-
Todd Rme