[python-committers] Re: core-dev chat

On 5/14/21 12:28 PM, Victor Stinner wrote: > Hi, > > I'm always connected to IRC #python-dev (Freenode) for 10 years, a few > other core devs use it time to time. Come to say hello ;-) > > The bugs.python.org and buildbot notifications are useful to me and I > don't feel annoyed by them. But

[python-committers] Re: Notification of a three-month ban from Python core development

Apparently there was agreement to hide this kind of information, and that's worse than the original behavior that was acted on. Who will be next? For what reason? I am not questioning the decision, at least we voted for our delegates, so I have to respect that decision even if I would disagree.

[python-committers] Re: Planning a hotfix Python 3.8.5

t; > - Ł > > > >> On 16 Jul 2020, at 20:00, Matthias Klose wrote: >> >> On 7/16/20 7:36 PM, Łukasz Langa wrote: >>> Hey team, >>> there are 3 security-related fixes in the 3.8 branch post 3.8.4, one with a >>> CVE, another with a pending CVE if I u

[python-committers] Re: Planning a hotfix Python 3.8.5

On 7/16/20 7:36 PM, Łukasz Langa wrote: > Hey team, > there are 3 security-related fixes in the 3.8 branch post 3.8.4, one with a > CVE, another with a pending CVE if I understood Steve correctly. I'd like to > release a hotfix 3.8.5 on Monday. > > Since this is a special security-focused

Re: [python-committers] OpenMandriva and Fedora abandoned Discourse for development discussions

On 27.02.19 22:11, Brett Cannon wrote: > On Tue, Feb 26, 2019 at 3:40 PM Victor Stinner wrote: > >> Hi, >> >> Follow-up of the previous "Can we choose between mailing list and >> discuss.python.org?" thread. >> >> Python isn't the first project who "experimented" Discourse to replace >> mailing

Re: [python-committers] Date for the Language Summit?

On 21.02.19 11:38, Victor Stinner wrote: > Hi, > > What will be the date of the Language Summit? I had to organize myself > very soon to get cheap flight and hotel, so I already booked > everything for Pycon US :-) +1 > Who will be allowed to attend? Will we have enough seats for all > CPython

Re: [python-committers] Python 4.0 or Python 3.10?

On 25.09.2018 21:30, Yury Selivanov wrote: > What's the current plan for what version of Python we release after 3.9? > > The reason I'm asking this is because I frequently need to refer to > *that version* of Python in the documentation, especially when I'm > deprecating APIs or behavior. Right

Re: [python-committers] Marking issues as "Release Blocker" priority (was Re: FINAL WEEK FOR 3.7.0 CHANGES!)

On 24.05.2018 20:09, Ned Deily wrote: > On May 24, 2018, at 13:46, Larry Hastings wrote: >> On 05/24/2018 10:08 AM, Ned Deily wrote: >>> If you (or anyone else) feels strongly enough about it, you should re-open >>> the issue now and make it as a "release blocker" and we

Re: [python-committers] RELEASED] Python 3.4.7rc1 and Python 3.5.4rc1 are now available

On 25.07.2017 10:37, Larry Hastings wrote: > And you can find Python 3.5.4rc1 here: > >https://www.python.org/downloads/release/python-354rc1/ > > > Python 3.4.7 final and Python 3.5.4 final are both scheduled for release on > August 6th, 2017. the build of the documentation fails with at

Re: [python-committers] Should I delay 3.5.3 and 3.4.6 by two weeks?

On 19.12.2016 06:26, Larry Hastings wrote: > > > Python 3.6.0 final just slipped by two weeks. I scheduled 3.5.3 and 3.4.6 to > ship about a month after 3.6.0 did, to "let the dust settle" around the > release. I expect a flood of adoption of 3.6, and people switching will find > bugs, and

Re: [python-committers] Here's what's going into 3.5.2 final and 3.4.5 final

On 24.06.2016 11:14, Larry Hastings wrote: > > > Heads up! This is a courtesy reminder from your friendly 3.4 and 3.5 release > manager. Here's a list of all the changes since 3.5.2rc1 that are currently > going into 3.5.2 final: > > * 155e665428c6 - Zachary: OpenSSL 1.0.2h build changes for

Re: [python-committers] The state of our copies of libffi (was: Redoing the C API?)

On 03.03.2016 21:58, Zachary Ware wrote: On Thu, Mar 3, 2016 at 12:38 PM, Brett Cannon wrote: [...] the maintenance issue we have with ctypes (or at least that's my hang-up with it). I think we still have not figured out what code we have patched and so no one has been

Re: [python-committers] changing the python version on the 2.7 branch

On 04/02/2015 07:38 AM, Nick Coghlan wrote: On 2 April 2015 at 05:05, Matthias Klose d...@ubuntu.com wrote: We'll have the 2.7.10 release in the coming months. This will be the first release with a two digit subminor version number, so please could we prepare for that early? Feature tests

[python-committers] changing the python version on the 2.7 branch

We'll have the 2.7.10 release in the coming months. This will be the first release with a two digit subminor version number, so please could we prepare for that early? Feature tests in python are unfortunately way too often based on version comparisons. Suggesting to push the following patch to

[python-committers] commit 93025:1c2c44313408 removed (at least) 2.7.9 NEWS entries

The commit 93025:1c2c44313408 removed almost all NEWS entries which were added after the 2.7.8 release. I didn't check for other files, but maybe somebody more familiar with this commit/merge should have a look. Matthias ___ python-committers mailing

Re: [python-committers] Status of the Derby, and request for another slip

Am 25.01.2014 14:09, schrieb Larry Hastings: I'd like to extend the Derby by two more weeks and add a fourth beta. In the past I did like the way how accurate the releases were planned and didn't slip at all, or only slip for a few days. This may sound a bit selfish, but a few Ubuntu developers

Re: [python-committers] Updated schedule for Python 3.4

Am 16.01.2014 12:17, schrieb Kristján Valur Jónsson: This is such an obvious question that it probably has been raised before, but anyway: Why not branch 3.4 earlier than release? That is how big projects are managed nowadays, you create a staging branch early. I'd suggest branching it off

Re: [python-committers] 2.7.2 and 3.1.4 rc now

On 05/31/2011 07:19 AM, Martin v. Löwis wrote: Really??? I have some changes that I need to commit to 2.7 that do need to go into 2.7.2. So how are you going to manage these? I rather recommend that the 2.7 branch is frozen until the final release, and any changes are only merged afterwards.

Re: [python-committers] updating libffi to 3.0.9?

On 24.02.2010 16:35, Ronald Oussoren wrote: On Wednesday, February 24, 2010, at 08:20AM, Thomas Hellerthel...@ctypes.org wrote: Matthias Klose schrieb: I would like to update the internal copy of libffi from the 3.0.5 release to 3.0.9 (plus an ARM specific patch checked in after the 3.0.9

Re: [python-committers] Misc/NEWS entries added to released versions

On 06.04.2009 00:33, Matthias Klose wrote: While looking at the diffs between the 261 release tags and the 26 branch, I noticed many items in Misc/NEWS appearing in the 2.6.1 or even 2.6 sections. I moved all of these to 2.6.2, after checking some of them, and found all of the checked ones

Re: [python-committers] Misc/NEWS entries added to released versions

On 13.09.2009 18:07, Gregory P. Smith wrote: On Sun, Sep 13, 2009 at 8:54 AM, Matthias Klosed...@debian.org wrote: On 06.04.2009 00:33, Matthias Klose wrote: While looking at the diffs between the 261 release tags and the 26 branch, I noticed many items in Misc/NEWS appearing in the 2.6.1

[python-committers] Misc/NEWS entries added to released versions

While looking at the diffs between the 261 release tags and the 26 branch, I noticed many items in Misc/NEWS appearing in the 2.6.1 or even 2.6 sections. I moved all of these to 2.6.2, after checking some of them, and found all of the checked ones be backported after the 2.6.1 release. Is there

Re: [python-committers] build dependency on the branches on sphinx trunk necessary?

Guido van Rossum schrieb: On Mon, Jan 26, 2009 at 1:59 PM, Matthias Klose d...@ubuntu.com wrote: Guido van Rossum schrieb: On Mon, Jan 26, 2009 at 1:27 PM, Matthias Klose d...@ubuntu.com wrote: Guido van Rossum schrieb: I'm not sure I understand your request. Is it okay to build docs using

[python-committers] build dependency on the branches on sphinx trunk necessary?

Hi, the requirement to build the documentation using a sphinx version from the trunk was merged to at least the 2.6 branch. This is clearly not a bug fix. Is it really necessary to rely on a trunk/unreleased version? Would it be possible to revert this change? Background: The Debian distribution