[python-committers] New triagers: Thomas Grainger and Michael Droettboom

Please welcome our newest triagers: Thomas Grainger, who is the maintainer of anyio and has been fixing asyncio bugs in the past three years. https://github.com/python/core-workflow/issues/471 Michael Droettboom, who is the creator of Pyodide (Python in the browser) and has helped to unblock

[python-committers] Re: Proposed tiered platform support

On 08/06/2022 21.21, Brett Cannon wrote: FYI there are now tier labels for the buildbots and the links have been added to the PEP. https://peps.python.org/pep-0011/#support-tiers Tier 2: https://buildbot.python.org/all/#/builders?tags=%2B3.x&t

[python-committers] Re: Consider adding a Tier 3 to tiered platform support

On 01/04/2022 01.40, Victor Stinner wrote: Hi, I don't think that the current PEP 11 draft (*) describes correctly the current status of a bunch of platforms which are not "actively" supported. I like to call these plaforms as "best effort support" platforms. I propose considering adding an expl

[python-committers] Re: Proposed tiered platform support

On 14/03/2022 19.37, Brett Cannon wrote: On Fri, Mar 11, 2022 at 5:04 PM Victor Stinner > wrote: Hi Brett, You can put my name as Contact of all Fedora and RHEL platforms. Note: Fedora "Rawhide" is the rolling release and it's common that these bu

[python-committers] Re: Proposed tiered platform support

On 11/03/2022 18.08, Marc-Andre Lemburg wrote: All other platforms === - Only code which either supports a higher-tier platform or is a general improvement may be checked in. My understanding of that sentence is: PRs which target platforms not listed in PEP 11 may not be check

[python-committers] Re: Proposed tiered platform support

On 11/03/2022 10.18, Marc-Andre Lemburg wrote: I think the list is missing some important platforms which we do support (looking at configure): * Linux on 32-bit ARM platforms, e.g. for Raspberry Pis * Linux on Android * AIX * Cygwin * NetBSD/OpenBSD * musl instead of glibc for Linux, e.g. for A

[python-committers] Re: Proposed tiered platform support

wasm32-unknown-emscripten XXX                        XXX                            Brett Cannon, Christian Heimes wasm32-unknown-wasi       XXX                        XXX

[python-committers] Re: Please make sure you're following good security practices with your GitHub account

On 16/06/2021 10.50, Antoine Pitrou wrote: > > Le 16/06/2021 à 10:33, Christian Heimes a écrit : >> On 16/06/2021 07.14, Julien Palard via python-committers wrote: >>> I do use a Yubikey too. >>> >>> Le 6/14/21 à 11:27 PM, Tim Peters a écrit : >>>&

[python-committers] Re: Please make sure you're following good security practices with your GitHub account

On 16/06/2021 07.14, Julien Palard via python-committers wrote: > I do use a Yubikey too. > > Le 6/14/21 à 11:27 PM, Tim Peters a écrit : >> If I buy one and plug it in, and that's the end of it, fine by me > > That's almost as simple as you want: > > - In Github settings 2FA tab you'll have to

[python-committers] Re: IMPORTANT: Python 3.10b2 release blockers

On 25/05/2021 00.45, Pablo Galindo Salgado wrote: > Hi, > > Tomorrow is the scheduled release of Python 3.10 beta 2 but > unfortunately we have several release blockers: > > https://bugs.python.org/issue44043 : > 3.10 b1 armhf Bus Error in hashlib test: test_gil

[python-committers] Re: Publish better than md5sums of Python builds?

On 16/03/2021 16.54, Julien Palard wrote: > Le 2021-03-16 à 15:52, Christian Heimes a écrit : >> could you please explain your use case? Which problem are you trying to >> solve? How would a sha256 checksum help you solve that problem? > > No, I'm just forwarding the su

[python-committers] Re: Publish better than md5sums of Python builds?

On 16/03/2021 14.59, Julien Palard via python-committers wrote: > Hi, > > Someone on Mastodon had me noticed that: > > => https://www.python.org/downloads/release/python-392/ > > gives the md5 sum of Python builds, and that we should probably do better. > > What about sha256? Has it been discus

[python-committers] Re: Is Tests / Ubuntu broken at the moment?

On 03/03/2021 18.59, Senthil Kumaran wrote: > On Wed, Mar 3, 2021 at 8:08 AM Christian Heimes wrote: > >> PEP 644 (not approved yet) and a soon-to-be-published PEP will hopefully >> get rid of the problem once and for all. PEP 644 removes support for >> OpenSSL < 1.1

[python-committers] Re: Is Tests / Ubuntu broken at the moment?

On 03/03/2021 21.54, Brett Cannon wrote: > Has this been submitted to the SC yet? I can't find an email or anything > at > https://github.com/python/steering-council/issues?q=is%3Aissue+is%3Aopen+644 > . Err ... no. I wa

[python-committers] Re: Is Tests / Ubuntu broken at the moment?

On 03/03/2021 16.06, Senthil Kumaran wrote: > On Tue, Mar 2, 2021 at 8:29 PM Gregory P. Smith wrote: >> >> For lack of better things to do with that... >> https://bugs.python.org/issue43382 filed to track it. > > Actually, that turned out to be useful. Thank you! > > The discussion with the def

[python-committers] Re: Welcome Batuhan Taskaya to the team!

Welcome Batuhan! ___ python-committers mailing list -- python-committers@python.org To unsubscribe send an email to python-committers-le...@python.org https://mail.python.org/mailman3/lists/python-committers.python.org/ Message archived at https://mail.p

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

On 23/07/2020 09.52, Matthias Klose wrote: > 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

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

On 22/07/2020 21.45, Ivan Levkivskyi wrote: > What's the point of sending this to everyone? Why wasn't this sent as a > quote? > Anyway, this doesn't change my decision. Hi Ivan, the message was sent to python-committers. All active Python core developers are subscribed to this mailing list and o

[python-committers] Re: 3.7.4 final delayed [Was: Python 3.7.4rc1 (and 3.6.9rc1) cutoffs ahead, now set for 2019-06-17]

On 29/06/2019 21.53, Ned Deily wrote: > On Jun 6, 2019, at 01:43, Ned Deily wrote: >> >> https://discuss.python.org/t/python-3-7-4rc1-and-3-6-9rc1-cutoffs-ahead-now-set-for-2019-06-17/1824 >> [...] >> Following the rc1 cutoff, changes merged to the >> 3.7 branch will be released in 3.7.5 three mon

[python-committers] Re: Zackery Spytz got the bug triage permission

On 07/06/2019 00.12, Victor Stinner wrote: > Hi, > > I decided to give more responsibilities to Zackery Spytz as a reward > for his hard commitment over the last year and a half into Python: I > gave him the bug triage permission. +1 I worked with him on a couple of bugs, e.g. the memfd_create.

Re: [python-committers] Fw: CoC violation (was: Retire or reword the "Beautiful is better than ugly" Zen clause)

On 20/09/2018 22.25, Antoine Pitrou wrote: > > Hi, > > I'm choosing to forward this to python-committers because I don't think > python-ideas is a reasonable place to discuss CoC decisions. > > I think the action taken by Brett (apparently decided with Titus and a > mysterious "conduct working g

Re: [python-committers] Fw: CoC violation (was: Retire or reword the "Beautiful is better than ugly" Zen clause)

On 21/09/2018 12.46, Antoine Pitrou wrote: > > Le 21/09/2018 à 02:06, Nathaniel Smith a écrit : >> Now sure, that taboo is an American thing, and I wouldn't support >> automatically banning someone who used it in genuine ignorance, was >> repentant when they realized what they'd done, etc. > > So

Re: [python-committers] 3.7.1 and 3.6.7 Releases Coming Soon

On 19/09/2018 23.12, Ned Deily wrote: > Update: not surprisingly, there have been a number of issues that have popped > up during and since the sprint that we would like to ensure are addressed in > 3.7.1 and 3.6.7. In order to do so, I've been holding off on starting the > releases. I think we

Re: [python-committers] New core developers: Lisa Roach and Emily Morehouse-Valcarcel

On 14/09/2018 12.28, Raymond Hettinger wrote: > At the developer sprints this week, we collectively decided to grant core > committer status to Emily and Lisa. > > Please join me in welcoming them to the team. Welcome on board! ___ python-committers m

Re: [python-committers] I have blocked someone from the Python org

+1 Thanks, Brett! ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] Language moratorium

On 2018-07-18 20:47, Barry Warsaw wrote: > On Jul 18, 2018, at 09:11, Stefan Krah wrote: > >> if I remember correctly, we had a moratorium for language changes around >> versions 3.2-3.3. I think during that time relatively few BDFL-level >> decisions were required. >> >> Perhaps we could have o

Re: [python-committers] Transfer of power

On 2018-07-12 20:50, Brett Cannon wrote: > IMHO the N-virate should primarily be responsible for delegation. > > Side note: I think we'll be talking less and less about language design, > and instead about library and infrastructure design. > > > Same here. I suspect this will make u

Re: [python-committers] Transfer of power

On 2018-07-12 20:02, Yury Selivanov wrote: > Another worry -- Guido knows mostly everything about all aspects of > Python design in all fields. To illustrate my point, I'm particularly > worried about async/await, asyncio/trio/twisted ecosystem -- so far it > seems that it's only Guido and I who'v

Re: [python-committers] Transfer of power

On 2018-07-12 16:57, Guido van Rossum wrote: > Now that PEP 572 is done, I don't ever want to have to fight so hard for > a PEP and find that so many people despise my decisions. > > I would like to remove myself entirely from the decision process. I'll > still be there for a while as an ordinary

Re: [python-committers] Triage perms for Elvis

On 2018-05-29 23:45, R. David Murray wrote: > At Yuri's request I've given Elvis triage privileges on the tracker. > I don't anticipate any objections, given the work he's done on > What's New and other things. +1 ___ python-committers mailing list pytho

Re: [python-committers] Proposing Mark Shannon to be a core developer

On 2018-05-14 16:41, Larry Hastings wrote: > > > Dr. Mark Shannon contributed the "key sharing dictionary" to Python, > writing both the PEP and the implementation.  This shipped in Python 3.3 > and was listed as one of the top features of that release as according > to the "What's New?" document

Re: [python-committers] Poll: Do you like the PEP 572 Assignment Expressions?

On 2018-05-02 11:49, Victor Stinner wrote: > Hi, > > I would like to start a poll on Chris Angelico's PEP 572 "Assignment > Expressions", restricted to Python core developers, to prepare the > talk at the Language Summit: > >https://www.python.org/dev/peps/pep-0572/ > > The poll is on the *c

Re: [python-committers] Welcoming Petr Viktorin as our newest core developer :)

On 2018-04-23 17:43, Ethan Furman wrote: > On 04/23/2018 07:39 AM, Nick Coghlan wrote: > >> With my recent proposal to accept Petr Viktorin as a specialist core >> developer focusing on extension module imports receiving several +1's >> and no concerns being raised, > > Where did this conversatio

Re: [python-committers] Proposing Petr Viktorin as a specialist core developer

On 2018-04-13 14:13, Nick Coghlan wrote: > Hi folks, > > I'd like to propose Petr Viktorin as a specialist core developer, > focusing on extension module imports. +1 I know him personally from work. He is a good engineer and responsible guy. Christian ___

Re: [python-committers] ssl module will require OpenSSL 1.0.2

On 2018-01-26 23:09, Christian Heimes wrote: > On 2018-01-26 23:03, Victor Stinner wrote: >> 2018-01-26 20:47 GMT+01:00 Christian Heimes : >>> LibreSSL does not yet implement these APIs yet >> >> Does it mean that Python 3.7 will not support OpenBSD anymore? Well, &g

Re: [python-committers] ssl module will require OpenSSL 1.0.2

On 2018-01-26 23:13, Victor Stinner wrote: > 2018-01-26 23:09 GMT+01:00 Christian Heimes : >> OpenBSD is still supported. But you either have to install OpenSSL, live >> without SSL support or get LibreSSL fixed. Python's test suite is >> passing without ssl available.

Re: [python-committers] ssl module will require OpenSSL 1.0.2

On 2018-01-26 23:03, Victor Stinner wrote: > 2018-01-26 20:47 GMT+01:00 Christian Heimes : >> LibreSSL does not yet implement these APIs yet > > Does it mean that Python 3.7 will not support OpenBSD anymore? Well, > it's not like OpenBSD support is perfect, but there a

[python-committers] ssl module will require OpenSSL 1.0.2

For your information, my ssl module improvement "Let OpenSSL verify hostname and IP address" will land either today or tomorrow. I'm just waiting for Alex to give me the final ACK on PR https://github.com/python/cpython/pull/3462. Once the PR has landed, several issues with hostname and IP addres

Re: [python-committers] Security: please enable 2-factor authentication on GitHub and your email

On 2017-12-12 02:17, Gregory P. Smith wrote: > On Mon, Dec 11, 2017 at 12:26 PM R. David Murray > wrote: > > On Mon, 11 Dec 2017 14:56:21 -0500, Donald Stufft > wrote: > > > > > On Dec 11, 2017, at 2:52 PM, R. David Murray >

Re: [python-committers] Official python-dev docker images

On 2017-12-07 19:00, Barry Warsaw wrote: > As part of the importlib_resources skunkworks project Brett and I have been > working on (just announced), we’ve also put together a nice Docker image that > we’re using for our automated testing. This image is based on Ubuntu 16.04 > and provides the

Re: [python-committers] Official python-dev docker images

On 2017-12-07 22:28, Barry Warsaw wrote: > That’s good feedback! I want to be clear about the purpose of this image, > both in that it’s blessed and maintained by us, and that its focus is on the > Python library and application developer (primarily for testing purposes). > > So maybe: Python.O

Re: [python-committers] Hacktoberfest

On 2017-09-28 18:21, Mariatta Wijaya wrote: > Hi, > > October is hacktoberfest (https://hacktoberfest.digitalocean.com/)  > In the month of October, people can sign up and contribute to open > source projects on GitHub. If they make 4 PRs during Hacktoberfest, > they'll earn a limited edition T-Sh

Re: [python-committers] UPDATE 1: Core sprint 2017 - Sep 4 - Sep 9, Menlo Park, California

On 2017-07-12 13:55, Łukasz Langa wrote: > Update: the sprint is on! > > *Good news*: Facebook is covering the venue, food and hotel costs. This > is confirmed. I'm working on getting a PSF grant for flights like last year. > > *Please book your* *airplane tickets* as soon as possible. Like last

Re: [python-committers] mention-bot is dead, long live the (misnamed) CODEOWNERS file!

On 2017-08-01 22:59, Brett Cannon wrote: > For those of you who have not noticed, mention-bot is no more. We were > using the free instance that Facebook provided, but it seems to have > fallen over and it doesn't look like it's going to get fixed soon > (https://github.com/facebook/mention-bot/iss

Re: [python-committers] Proposing Carol Willing to become a core developer

+1 from me We need more experienced mentors and doc writers. Sent from my Android phone with K-9 Mail.___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.

Re: [python-committers] Github reviews are cannibalizing BPO

On 2017-05-03 19:54, Brett Cannon wrote: > I just touched > up https://github.com/python/cpython/blob/master/.github/CONTRIBUTING.rst to > explicitly mention that only code review issues should be discussed on > GitHub. Thanks Brett! I followed Donalds' advice and just pushed a modification to .m

Re: [python-committers] Github reviews are cannibalizing BPO

On 2017-05-02 20:28, Terry Reedy wrote: > On 5/2/2017 10:07 AM, R. David Murray wrote: >> On Tue, 02 May 2017 09:36:02 +0200, "M.-A. Lemburg" >> wrote: > >>> IMO, it's much easier for everyone to just always point people >>> to BPO for discussions and keep PRs reserved for code reviews. >> >> I a

[python-committers] Github reviews are cannibalizing BPO

Hi all, since our move to Github I noticed a major increase in incoming patches. I like it. It clearly shows that it was a good decision. But I don't like the fact that Github reviews are cannibalizing issues on BPO. Before the migration decisions regarding a new feature or bug fix were made on t

Re: [python-committers] Date of the Language Summit at Pycon US 2017?

On 2017-02-24 11:30, Victor Stinner wrote: > Hi, > > I'm going to book my hotel and flight for Pycon US, but I don't know > the date of the Language Summit and I would prefer to not miss it if > possible :-) > > Does someone organize it? The language summit is usually on the first day of tutoria

Re: [python-committers] Proposed new core developer -- Mariatta Wijaya

On 2017-01-26 14:49, Nick Coghlan wrote: > With Raymond volunteering as mentor, I think an approach where changes > are still reviewed, but it's Mariatta that does the final commit would > work. +1 I followed some of Mariatta's work. She does a good job. I trust both her and Raymond's judgement t

Re: [python-committers] Call For Participants For The 2016 Python Language Summit

On 2016-03-03 08:45, Nick Coghlan wrote: > On 2 March 2016 at 11:01, Larry Hastings wrote: >> It's that time once again: time to start planning for the 2016 Python >> Language Summit! > > Huzzah, thanks for organising this again! > > I've forwarded the email to a few folks to suggest they submit

Re: [python-committers] Anyone up for a core dev panel discussion at EuroPython 2016 ?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-02-19 17:35, M.-A. Lemburg wrote: > Hello all, > > at this year's EuroPython we'll have a new officially supported > feature, the panel discussion, and we (I'm one of the organizers) > thought it would be big fun to have a panel of core de

Re: [python-committers] You are invited to the Pycon 2015 Language Summit

On 21.01.2015 17:54, Barry Warsaw wrote: > *Please* let us know if you plan to attend so we can size the room and other > amenities accordingly. I'll be there for the first time. It's also my first time at PyCon US and first time outside Europe thanks to the financial aid program. My current plan

Re: [python-committers] MSDN renewals

ll you, but they are required fields). Hi Brian, my MSDN subscription wasn't renewed yet. Can you have a look, please? Visual Studio Ultimate with MSDN Christian Heimes, si...@cheimes.de Subscriber ID:600694836 Status: Expired/In grace period Expired on 2/14/2014 Christian __

Re: [python-committers] PyCon Language Summit: Wednesday 9th April

Am 04.12.2013 20:07, schrieb Benjamin Peterson: > FWIW, the current plan is to have the last normal release in 2015 > and security releases "indefinitely" (2020 or something like > that). Can we make an exception for platform support, e.g. compatibility fixes with new compiler or library versions?

Re: [python-committers] PyCon Language Summit: Wednesday 9th April

Am 04.12.2013 19:14, schrieb Michael Foord: > > On 4 Dec 2013, at 18:13, Christian Heimes > wrote: > >> Am 04.12.2013 19:01, schrieb Michael Foord: >>>> I've added it to the agenda with your name... >>>> >>>> As my name is being

Re: [python-committers] PyCon Language Summit: Wednesday 9th April

Am 04.12.2013 19:01, schrieb Michael Foord: >> I've added it to the agenda with your name... >> >> As my name is being attached to a discussion of ending the >> development of Python 2, will there be a place for people to >> check their pitchforks at the door? =) >> > > On the contrary, I think

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

Am 29.11.2013 21:05, schrieb Guido van Rossum: > Here's another idea. Ban him temporarily from the tracker and the > lists(*) and tell him that to be unbanned he has to talk to me, and > to me only. I will then negotiate a cool-off period and posting > guidelines with him. If he violate those he w

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

Am 29.11.2013 19:14, schrieb Guido van Rossum: > Have you read the latest on the python-dev thread? Several other > people are now also complaining. The only thing that makes sense to > me is nothing -- banning Anatoly now is just going to cause a PR > disaster. Not responding at all will most like

Re: [python-committers] Anatoly has been warned about his behaviour potentially leading to his loss of tracker privileges

Am 29.11.2013 16:04, schrieb Brett Cannon: > I just want to make sure others know that Georg has warned Anatoly > that if he continues to re-open a specific issue he will lose his > tracker privileges (http://bugs.python.org/issue19822#msg204696). I > stand behind his warning and will support anyon

[python-committers] Fwd: Re: Fwd: Python at HackerOne

Here is another mail from Alex. I asked him about conflict of interest: Original-Nachricht Betreff:Re: Fwd: Python at HackerOne Datum: Thu, 7 Nov 2013 17:33:52 -0800 Von:Alex Rice An: Christian Heimes Our "easy fix" to the collusion issue is

[python-committers] Fwd: Re: Python at HackerOne

Forwarded mail Original-Nachricht Betreff:Re: Python at HackerOne Datum: Thu, 7 Nov 2013 16:37:30 -0800 Von:Alex Rice An: Christian Heimes Kopie (CC): python-committers@python.org, IBB Panel Hi Christian! Thanks for getting in touch, glad there&#

[python-committers] Python at HackerOne

hanks a lot for including Python! Is there anything the PSRT or Python Software Foundation can do to join the effort and assist with your program? I think it's in our mutable interest to spread the word and handle incoming security issues properly. We will be glad to help you. Regards, Christ

Re: [python-committers] Python bug bounty

Am 07.11.2013 11:45, schrieb M.-A. Lemburg: > On 07.11.2013 11:40, Christian Heimes wrote: >> Hi, >> >> this is going through the news right now. Has anybody contact us about >> the bug bounty program for Python? >> >> https://hackerone.com/python > &g

[python-committers] Python bug bounty

Hi, this is going through the news right now. Has anybody contact us about the bug bounty program for Python? https://hackerone.com/python Christian ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listi

Re: [python-committers] Zachary Ware for commit access?

Am 01.11.2013 04:50, schrieb Brian Curtin: > Hi all, > > What do you think about giving commit access to Zachary Ware? He's > been active on the tracker for a while and has contributed a good bit > of Windows code. +1 for a new Windows developer. :) __

Re: [python-committers] PEP commit privilieges for Donald Stufft?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Am 14.08.2013 18:49, schrieb Nick Coghlan: > Donald is the current main developer for PyPI and is doing a lot > of work on PyPI related PEPs this days - it would reduce the > administrative overhead if he could update the related PEPs > directly. >

[python-committers] Interview with Coverity

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, Kristin Brennan from Coverity has asked me for an interview about Python core development and how we are using Coverity Scan. Coverity is planing to have a monthly series of interviews with open source projects that use their service, for exa

Re: [python-committers] SSH fingerprint

Am 25.03.2013 05:51, schrieb Jeffrey Yasskin: > You missed that ECDSA != DSA. Yeah, Elliptic Curve DSA is as secure as RSA while using much shorter keys. ECDSA verification used to be much slower so you may want to prefer RSA for short time connections like hg pull and push. Christian ___

Re: [python-committers] Anatoly Techtonik's contribution

Am 25.12.2012 13:37, schrieb Nick Coghlan: > I'm well and truly to the point of caring far more about the feelings > of people who get frustrated trying to deal with his obtuseness > (whether that arises deliberately or through genuine cluelessness) > than I care about his feelings. He has the enti

Re: [python-committers] anyone still have access to the coverity scan results?

Am 19.08.2012 18:02, schrieb Brett Cannon: > The link to their build tools is http://scan.coverity.com/self-build/ . > So it looks like we have to give them the files to analyze now after we > have built them with their tool chain on LInux. Yes, that's what I'm talking about. It took me a while to

Re: [python-committers] anyone still have access to the coverity scan results?

Am 18.08.2012 15:08, schrieb Stefan Krah: > Christian Heimes wrote: >> Yup, my login still works. I can send you a CSV or XML report if you like. > > Thanks, got the CSV! > > If anyone has the possibility to create new accounts, I would like to apply > for one.

Re: [python-committers] anyone still have access to the coverity scan results?

Am 18.08.2012 11:53, schrieb Stefan Krah: > Antoine Pitrou wrote: >> Besides, if the coverity results are private and limited to a couple of >> core devs, I don't think other sprinters will benefit a lot from such >> "education". Or do you have something particular in mind? > > What is the status

Re: [python-committers] Why r69846 is not merged to "release26-maint"?

Georg Brandl schrieb: > David Goodger schrieb: >> On Thu, Jul 2, 2009 at 14:56, R. David Murray wrote: >>> I can see it now...the TV and movie track at PyCon 2010, >>> with attendance mandatory for anyone wanting to participate >>> in the Core sprint... >> We actually had a room or two for evening

Re: [python-committers] Why r69846 is not merged to"release26-maint"?

Barry Warsaw wrote: > I will announce this to py-list, py-ann, and update the 3.0 download pages. > > There will be no 3.0.2. +1 for your decision. Are there any known incompatibilities that could break a Python 3.0 script on 3.1? ___ python-committers

Re: [python-committers] svnmerge

Antoine Pitrou schrieb: > Le dimanche 01 mars 2009 à 21:08 +0100, "Martin v. Löwis" a écrit : >> I meant that as a relative qualification indeed (merging a single >> revision specified on the command line as opposed to merging all >> available versions). >> >> I just measured merging r70081, and it

Re: [python-committers] Survey about DVCSs compared to svn

Nick Coghlan schrieb: > Georg Brandl wrote: >> It doesn't only *feel* slow, it *is* slow. And not only compared to merging >> with a DVCS, which doesn't need network. Half a minute to merge a three-line >> change is not productive. > > Don't forget that *blocking* a revision with svnmerge seems

Re: [python-committers] Survey about DVCSs compared to svn

Nick Coghlan wrote: > Bob Ippolito wrote: >> I have more or less the same opinion as Guido regarding svn merge. It >> sucks. We bump up against problems with svn merge tracking on a >> regular basis at work. We'd have switched to a DVCS by now if it >> wasn't for tool support (trac mostly) and the

Re: [python-committers] I've got a surprise for you!

Trent Nelson schrieb: > Catchy subject eh? Unless, of course, you've seen Forgetting Sarah > Marshall, in which case, it's probably a tad disturbing. > > Nevertheless, I do have a surprise for everyone. I spent a lot of > time early last year trying to keep the buildbots green, e

Re: [python-committers] Luke Kenneth

Guido van Rossum schrieb: > Is anyone else frustrated by Luke Kenneth Casson Leighton's rants in > python-dev? It seems he is living on another planet to me. Or am I > seeing it all wrong? You are seeing it perfectly right. I'm astonished that nobody has reacted and kicked him from the list so far

Re: [python-committers] trying again...

Barry Warsaw wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Nov 6, 2008, at 8:27 PM, Barry Warsaw wrote: 3.0 branch frozen. Ping me on irc if you need to make commits. No go, the docs are still broken. I've re-opened issue 4266 and will try to ping Georg in my tomorrow morning.

Re: [python-committers] broken arm

Jesus Cea wrote: I just have broken my left arm last saturday (sliding swimming pools are dangerous :)). I will be barely online for the next 6 weeks. I will try to keep email backlog under control, but single-hand typing is a nightmare. Take the opportunity and read some good books! :] And get

Re: [python-committers] python 3.0 compilation warning in Objects/stringlib/find.h

Amaury Forgeot d'Arc wrote: Hello, r65977 was not correctly merged into py3k; I get the following compilation warning: Objects/stringlib/find.h:93:36: warning: extra tokens at end of #ifdef directive And indeed, the line #ifdef STRINGLIB_WANT_CONTAINS_OBJ && !defined(FROM_BYTEARRAY) does not

Re: [python-committers] ubuntu release plan

Anthony Baxter wrote: What would this professionalisation get us that we don't have now? As far as I can see, the biggest hole at the moment (as always) is with people to trawl the tracker and triage bug reports and patches. It would get us one or some developers who can work 8+ hours a day, fi

Re: [python-committers] PQM?

Barry Warsaw wrote: Let me take this opportunity to explicitly say that I'm not /blaming/ anybody for this. I consider the problems we had with the module an indication of a systemic, team-wide deficiency. I greatly appreciate you (and others) working so hard to land it and make it work. He

Re: [python-committers] ubuntu release plan

Antoine Pitrou wrote: Ubuntu's sophisticated release plan is certainly justified by its business model, and the desire to both appeal to the open source people and the corporate people without creating two different distributions. I don't think Python has the same business requirements (neither

Re: [python-committers] PQM?

Barry Warsaw wrote: Unfortunately, they're not being solved without PQM either! Really, we've had to delay releases several times because the branches were broken across multiple operating systems. Pleading on the mailing lists doesn't help. Hanging out on irc doesn't help. Having Benjamin,

Re: [python-committers] PQM?

Guido van Rossum wrote: [Hey Christian, welcome back! (It seems we hadn't heard much from you for a while...)] Yeah, I had an acute case of burnout syndrome. I tried to do far too many things in parallel. I prescribed myself to focus on the most important tasks like my new apartment and my jo

Re: [python-committers] PQM?

Barry Warsaw wrote: I think this is a case where PQM might have helped. Assuming the build/test would uncover these subtle bugs, the multiprocessing code would not have landed. You would then probably publish a branch with d t those (failing) changes and rally the help you needed to fix those

Re: [python-committers] PQM?

Barry Warsaw wrote: PQM = Patch Queue Manager Basically, it's a robot that controls commits to the trunk. Nothing lands in the trunk without getting through PQM first. PQM serializes changesets so that they must apply cleanly with no conflicts, and pass the entire test suite. There could b

Re: [python-committers] Nominate Hirokazu Yamamoto (oceancity) for commit privs.

Trent Nelson wrote: What do people think about making Hirokazu Yamamoto a committer? I rarely see any mailing list posts from him, but he sure makes up for it in terms of patches submitted to the issue tracker. As far as I can tell (I've noticed his regular involvement via patches and whatno