[python-committers] Re: list of core-devs, triagers, etc.

Does https://github.com/python/voters/ suffice? On Sun, Feb 13, 2022, at 19:16, Ethan Furman wrote: > Greetings! > > Is there a list somewhere of the core developers and triagers? > > I'm looking to prune the core-mentorship subscriber list as I'm > confident 90%+ are folks that wanted help learn

[python-committers] Re: Do I qualify for a x...@python.org email

For future reference, the policy is documented here: https://www.python.org/psf/records/board/policies/email/ On Sat, Oct 2, 2021, at 13:11, Joannah Nanjekye wrote: > Thanks Mariatta > > On Sat, Oct 2, 2021 at 3:07 PM Mariatta wrote: >> Hi Joannah, >> >> Yes you can request the email address by

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

On Wed, Mar 17, 2021, at 09:29, Victor Stinner wrote: > On Tue, Mar 16, 2021 at 9:16 PM Gregory P. Smith wrote: > > The benefit of listing the sha256 for files is that it prevents this > > question coming up again and again because md5 is old and rightfully on the > > "never use" list for man

[python-committers] Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues

On Wed, Sep 11, 2019, at 00:32, Steven D'Aprano wrote: > On Tue, Sep 10, 2019 at 09:49:00AM +0100, Benjamin Peterson wrote: > > > > > > On Tue, Sep 10, 2019, at 06:54, Raymond Hettinger wrote: > > > Another essential bit of tooling for the migration: > &

[python-committers] Re: Make AppVeyor CI non-mandatory during the CPython sprint?

On Tue, Sep 10, 2019, at 08:54, Victor Stinner wrote: > Le lun. 9 sept. 2019 à 18:46, Benjamin Peterson a écrit > : > > No one could think of a reason not to replace AppVeyor with Azure, so I've > > gone ahead and done that on all those branches. > > Here is a r

[python-committers] Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues

On Tue, Sep 10, 2019, at 06:54, Raymond Hettinger wrote: > Another essential bit of tooling for the migration: > > * Before filing a bug report or feature request, we ask people to > search to see if there is already an issue in progress or a resolved > issue on the topic. We need to make s

[python-committers] Re: Make AppVeyor CI non-mandatory during the CPython sprint?

On Mon, Sep 9, 2019, at 20:15, Terry Reedy wrote: > On 9/9/2019 12:46 PM, Benjamin Peterson wrote: > > > > > > On Mon, Sep 9, 2019, at 16:50, Victor Stinner wrote: > >> Hi, > >> > >> I see a high activity on pull requests on the CPython pr

[python-committers] Re: Make AppVeyor CI non-mandatory during the CPython sprint?

On Mon, Sep 9, 2019, at 16:50, Victor Stinner wrote: > Hi, > > I see a high activity on pull requests on the CPython project, likely > because of the CPython sprint. Sadly, the AppVeyor is still slow and > still has only 2 jobs in parallel. Yeah, there has been quite some crankiness about this

Re: [python-committers] [Python-Dev] Farewell, Python 3.4

rs of the release team that worked on > Python 3.4: > > > Georg Brandl > > > Julien Palard > > > Martin von Löwis > > > Ned Deily > > > Steve Dower > > > Terry Reedy > > > and all the engineers of the Python infrastructure team. >

Re: [python-committers] discuss.python.org participation

On Fri, Oct 12, 2018, at 11:55, Brett Cannon wrote: > On Thu, 11 Oct 2018 at 01:30, Antoine Pitrou wrote: > > > > > What concerns me is that there are several long-time and/or prominent > > developers who are not even registered (*) on discuss.python.org. For >

Re: [python-committers] Recent buildbot.python.org changes

On Fri, Sep 14, 2018, at 14:02, Zachary Ware wrote: > Hi all, > > Most of my effort this week has gone into improving the state of > buildbot.python.org, which has largely gone into improving Buildbot > itself. Here are the relevant highlights: > > - Anyone can now log into buildbot.python.or

Re: [python-committers] Visual Studio Team Services checks on pullrequests

On Wed, May 16, 2018, at 15:27, Steve Dower wrote: > Thanks Microsoft for the 20 concurrent builds on Windows, macOS and Linux :) That is quite generous! Will it be ongoing? ___ python-committers mailing list python-committers@python.org https://mail.p

Re: [python-committers] Can we delete https://hg.python.org/coding/cpython/?

Killed. On Mon, Dec 19, 2016, at 14:23, Brett Cannon wrote: > It's erroneously labeled as the "official python repo" and created by > some > stranger. > ___ > python-committers mailing list > python-committers@python.org > https://mail.python.org/mailman

Re: [python-committers] autoconf 2.70

The correct way to solve this is probably to stop checking in the generated configure and generate it with a "blessed" autoconf version in the release tarballs. On Sun, Sep 11, 2016, at 13:17, Xavier de Gaye wrote: > On 07/22/2016 06:41 PM, Brett Cannon wrote: > > > > > > On Fri, 22 Jul 2016 at

Re: [python-committers] We will be moving to GitHub (hopefully) in 2016

Brett, thank you very much for putting your (vacation!) time into this. On Fri, Jan 1, 2016, at 11:24, Brett Cannon wrote: > If you want to read the reasons I chose GitHub over GitLab, see > https://mail.python.org/pipermail/core-workflow/2016-January/000345.html > . > If you want to discuss the d

Re: [python-committers] Committer missing :)

Indeed, if you have no keys around, the (automatically generated) committers.txt file will not list you. On Sun, Dec 6, 2015, at 17:05, Jesus Cea wrote: > I was trying to push a patch but it seems I am not a committer anymore. > My name vanished of and the >

Re: [python-committers] PSA: replace your DSA keys for SSH

On Wed, Oct 7, 2015, at 19:38, Tim Peters wrote: > [Benjamin Peterson ] > > As a followup to this, I have now removed all DSA keys. People who only > > had DSA keys will need to submit new keys to hgaccounts@. > > That apparently was addressed to me - cool ;-) > > J

Re: [python-committers] PSA: replace your DSA keys for SSH

On Wed, Oct 7, 2015, at 18:52, Raymond Hettinger wrote: > > > On Oct 6, 2015, at 11:43 PM, Benjamin Peterson wrote: > > > > As a followup to this, I have now removed all DSA keys. People who only > > had DSA keys will need to submit new keys to hgaccounts@. >

Re: [python-committers] PSA: replace your DSA keys for SSH

As a followup to this, I have now removed all DSA keys. People who only had DSA keys will need to submit new keys to hgaccounts@. On Thu, Aug 27, 2015, at 13:36, Georg Brandl wrote: > Hi all, > > newer OpenSSH versions (7.0+) default to not allowing ssh-dss keys for > public key authentication.

Re: [python-committers] SSH problems attempting to access hg.python.org

What does `ssh-add -L` give? ssh basically throws keys at the server until the server accepts it. The server has a limit of two attempts, so if have more than two keys in your agent, problems result. On Thu, Oct 1, 2015, at 01:57, Nick Coghlan wrote: > Hi folks, > > After getting some publickey e

Re: [python-committers] PSA: replace your DSA keys for SSH

On Thu, Aug 27, 2015, at 16:36, Donald Stufft wrote: > On August 27, 2015 at 4:37:21 PM, Georg Brandl (g.bra...@gmx.net) wrote: > > Hi all, > > > > newer OpenSSH versions (7.0+) default to not allowing ssh-dss keys for > > public key authentication. If you experience "permission denied" errors,

Re: [python-committers] Weak SSH keys

On Wed, Jun 3, 2015, at 08:31, Antoine Pitrou wrote: > > > Le 03/06/2015 15:27, Benjamin Peterson a écrit : > > > > > > On Wed, Jun 3, 2015, at 08:21, Antoine Pitrou wrote: > >> > >> Le 02/06/2015 18:42, Benjamin Peterson a écrit : > >&g

Re: [python-committers] Weak SSH keys

On Wed, Jun 3, 2015, at 08:21, Antoine Pitrou wrote: > > Le 02/06/2015 18:42, Benjamin Peterson a écrit : > > > > > > On Tue, Jun 2, 2015, at 12:37, Antoine Pitrou wrote: > >> Le 02/06/2015 18:28, Benjamin Peterson a écrit : > >>> >

Re: [python-committers] Weak SSH keys

On Tue, Jun 2, 2015, at 12:35, Skip Montanaro wrote: > On Tue, Jun 2, 2015 at 11:28 AM, Benjamin Peterson > wrote: > > Also, everyone should use ed25519 keys now. :) > > For people like myself who are behind the curve, can someone point me > to a primer on generating new,

Re: [python-committers] Weak SSH keys

On Tue, Jun 2, 2015, at 12:37, Antoine Pitrou wrote: > Le 02/06/2015 18:28, Benjamin Peterson a écrit : > > > > Also, everyone should use ed25519 keys now. :) > > Depends if the servers you connect to have all been migrated to a recent > enough OpenSSH. SSH can us

Re: [python-committers] Weak SSH keys

On Tue, Jun 2, 2015, at 11:19, A.M. Kuchling wrote: > Someone ran an experiment looking at the SSH keys used on GitHub > (public keys are accessible through the API): > > https://blog.benjojo.co.uk/post/auditing-github-users-keys > > Excerpt: > > I remembered back to the May 2008 Debian

Re: [python-committers] Do people prefer pushing feature repos or one massive patch?

On Wed, Apr 1, 2015, at 12:09, Brett Cannon wrote: > The implementation for PEP 488 is basically done (sans Windows installer > stuff). I did the work in a features repo at > https://hg.python.org/features/pep-488/ . Once I have addressed reviewer > comments at http://bugs.python.org/issue23731 ,

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

On Fri, Oct 17, 2014, at 10:55, Matthias Klose wrote: > 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. I've just pushed a co

Re: [python-committers] Mark Lawrence

On Sun, Oct 5, 2014, at 14:42, Serhiy Storchaka wrote: > On 05.10.14 21:15, Benjamin Peterson wrote: > > "BreamoreBoy" is back on tracker touching hundreds of issues without > > adding any new information. This is certainly not the first time. Can we > > ban him?

[python-committers] Mark Lawrence

"BreamoreBoy" is back on tracker touching hundreds of issues without adding any new information. This is certainly not the first time. Can we ban him? ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo

Re: [python-committers] Commit rights for Robert Collins

hgaccou...@python.org On Sat, Oct 4, 2014, at 01:39, Michael Foord wrote: > > On 24 Sep 2014, at 00:01, R. David Murray wrote: > > > On Mon, 22 Sep 2014 10:51:27 +0100, Michael Foord > > wrote: > >> Robert Collins is volunteering to help with maintenance and improvement > >> of unittest. He'

Re: [python-committers] [Python-Dev] new hg.python.org server

On Fri, Sep 12, 2014, at 21:52, Shorya Raj wrote: > Just wondering - are there any sys-adminy sort of tasks that could be > completed? I mean, I have some (note, some) experience doing this, and I > wouldn't mind helping out (I inquired in the buildbot thread as well, but > there wasn't much of a

[python-committers] new hg.python.org server

I just switched hg.python.org from a OSUOSL VM to a Rackspace VM. The new VM is a bit beefier and has what I think is better network connectivity, so hopefully that will improving the speed of repository operations. We also now support HTTPS for repository browsing and cloning, so update all your l

Re: [python-committers] Contact info for possible workflow tool security issue

On Thu, Jun 19, 2014, at 18:23, Antoine Pitrou wrote: > > > Le 19/06/2014 21:13, Nick Coghlan a écrit : > > A colleague spotted a possible security issue with one of the CPython > > workflow tools (specifically with the configuration of our > > installation, rather than with the upstream project)

Re: [python-committers] default hg.python.org/cpython is now 3.5

On Mon, Mar 17, 2014, at 7:10, Brett Cannon wrote: > On Mon, Mar 17, 2014 at 4:51 AM, Victor Stinner > wrote: > > > Until when should we fix bugs in the branch 3.3? Branches 3.1 and 3.2 only > > accept security fixes, right? > > > > Typically we do one last release before shutting the last bugf

Re: [python-committers] Python Language Summit: please rsvp

I'll have to turn you down. Thanks, though. On Thu, Feb 20, 2014, at 01:06 PM, Michael Foord wrote: > Hey all, > > The Python Language Summit is on Wednesday 9th April, prior to PyCon in > Montreal. The summit will be from 10am to approximately 4pm. If you want > to attend you *must* let me know

Re: [python-committers] Commit access for Yury Selivanov?

On Wed, Jan 22, 2014, at 07:01 PM, Nick Coghlan wrote: > On 20 January 2014 14:39, Nick Coghlan wrote: > > > > On 20 Jan 2014 08:06, "Victor Stinner" wrote: > >> > >> Is it enough to know the python process and how to write good patches? I > >> don't see why Yury would become but not Vajrasky Kok

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

On Thu, Jan 16, 2014, at 06:03 PM, Kristján Valur Jónsson wrote: > I never got the impression that this was a matter of funding, Nick. > And while I completely understand that core developers enjoy working in 3 > much more, it was decided to not accept any improvements for a +2.7 > version even fro

Re: [python-committers] 3.3.4 planning

On Thu, Jan 16, 2014, at 06:30 AM, Georg Brandl wrote: > Hi all, > > I'm planning to release 3.3.4 candidate 1 together with 3.4 beta 3, i.e. > on > the 26th -- and then 3.3.4 final two weeks later if nothing bad comes up. > > As always, there will be one more full 3.3 release after 3.4 final, >

Re: [python-committers] clinic churn after beta2

On Tue, Jan 7, 2014, at 06:06 PM, Nick Coghlan wrote: > On 8 Jan 2014 08:44, "Eric V. Smith" wrote: > > > > On 1/7/2014 7:33 PM, Benjamin Peterson wrote: > > > A PyPI module is not so great because you'll have to change every > > > formatting opera

Re: [python-committers] clinic churn after beta2

On Tue, Jan 7, 2014, at 04:29 PM, Nick Coghlan wrote: > On 8 Jan 2014 07:11, "A.M. Kuchling" wrote: > > > > On Tue, Jan 07, 2014 at 02:37:22PM -0800, Eli Bendersky wrote: > > > Just to be clear, this is exactly what I mean. I'm not saying AC is not > > > worth it; I'm questioning the timing. > > >

Re: [python-committers] svn.python.org SSL cert is expired

I was going to get another CACert certificate for svn.python.org, but I forgot you need to verify the domain (by getting email at root@) before CACert will issue a cert for it. I suppose I could generate another self-signed one. 2013/12/25 R. David Murray : > So all the buildbots are red for the m

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

2013/12/4 Christian Heimes : > 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

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

2013/12/4 Barry Warsaw : > On Dec 04, 2013, at 07:15 PM, Antoine Pitrou wrote: > >>As for the question, I think we should wait at least two or three years >>before "sunsetting" 2.7. > > I've been thinking we should move Python 2.7 to security-fix only around the > Python 3.5 time frame, with a coup

[python-committers] 2.7.6

I know I said I would do Python 2.7.6 this weekend, but I became unexpectedly busy. I will plan to get to it in the next few days. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listi

Re: [python-committers] Closing the 2.6 branch?

2013/10/30 Barry Warsaw : > Now that 2.6.9 is out, I wonder if there's anything we can or should do to the > Mercurial repository to explicitly prevent commits to the 2.6 branch? We have > we done to older branches? I've now disabled pushing to the 2.6 branch. -- Regards, Benjamin ___

Re: [python-committers] [Python-Dev] Python 3.4.0a4: Coming In For A Bumpy Landing

2013/10/20 Ned Deily : > > On Oct 20, 2013, at 15:57 , Benjamin Peterson wrote: > >> 2013/10/20 Larry Hastings : >>> >>> >>> 3.4.0a4 is tagged and I'm in the process of releasing it. But it's going to >>> be, let's say, mor

Re: [python-committers] [Python-Dev] Python 3.4.0a4: Coming In For A Bumpy Landing

2013/10/20 Larry Hastings : > > > 3.4.0a4 is tagged and I'm in the process of releasing it. But it's going to > be, let's say, more "alpha-quality" than the previous alphas. > > Known problems: > > There's a reference count leak in the compiler. This is fixed, so you could just move the tag up a

Re: [python-committers] Timeframe for 2.7.6

Fall 2013. 2013/8/16 Jesus Cea : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Is there any release date/estimation for 2.7.6?. > > - -- > Jesús Cea Avión _/_/ _/_/_/_/_/_/ > j...@jcea.es - http://www.jcea.es/ _/_/_/_/ _/_/_/_/ _/_/ > Twit

Re: [python-committers] Can I get the keys to the website please?

You should already have access to the website repo. 2013/8/3 Larry Hastings : > > > PEP 101 tells me that in order to release Python 3.4.0a1 I must massage the > website. I foolishly left this to the last minute. Can anybody give me > access to the repo and shove me towards the README? Pretty p

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

You can just pull. 2013/7/16 Barry Warsaw : > On Jul 16, 2013, at 09:31 AM, Benjamin Peterson wrote: > >>Oops, the bad one is actually >> >>8889c9b5dd3a > > Uh, then how do we unstrip the other one? Or should we just re-clone and > ignore

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

Oops, the bad one is actually 8889c9b5dd3a 2013/7/16 Ronald Oussoren : > > On 16 Jul, 2013, at 18:03, Benjamin Peterson wrote: > >> It should be safe to continue pulling. Those revisions you see below >> are ones committed after I stripped the repo. > > Isn&#

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

You should be completely safe if you didn't pull at all yesterday. 2013/7/16 Terry Reedy : > > > On 7/15/2013 11:46 PM, Benjamin Peterson wrote: >> >> If you have c3a510b22218 in your repo, you will need to strip it like this >> >> $ hg strip c3a510b22218 >

Re: [python-committers] IMPORTANT: Strip your repos if you pulled recently

It should be safe to continue pulling. Those revisions you see below are ones committed after I stripped the repo. 2013/7/16 Ronald Oussoren : > > On 16 Jul, 2013, at 5:46, Benjamin Peterson wrote: > >> If you have c3a510b22218 in your repo, you will need to strip it like this &

Re: [python-committers] I would suggest not pushing or pulling from the repo

Okay, I fixed the repo. You may need to strip your repo per my last mail. 2013/7/15 Benjamin Peterson : > I accidently pushed a merge from 3.3 to default in the "3.3" branch. I > think I'm going to have to strip it. > > -- > Regards, >

[python-committers] IMPORTANT: Strip your repos if you pulled recently

If you have c3a510b22218 in your repo, you will need to strip it like this $ hg strip c3a510b22218 (make sure to have the mq extension enabled) Sorry for the trouble. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.o

Re: [python-committers] I would suggest not pushing or pulling from the repo

thon-committers [mailto:python-committers- >> bounces+jaraco=jaraco@python.org] On Behalf Of Benjamin Peterson >> Sent: Monday, 15 July, 2013 23:08 >> To: python-committers >> Subject: [python-committers] I would suggest not pushing or pulling from >> the repo >&

[python-committers] I would suggest not pushing or pulling from the repo

I accidently pushed a merge from 3.3 to default in the "3.3" branch. I think I'm going to have to strip it. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Policy for committing to 2.7

2013/6/25 Larry Hastings : > I'm not questioning the decision--I'm asking, what is the heuristic I can > apply in the future to predict whether or not a change will be accepted into > the 2.7 branch. My current heuristic ("only bad bug fixes") seems to be on > the fritz. I realize everyone wants

Re: [python-committers] Policy for committing to 2.7

2013/6/22 Eli Bendersky : > Yes, this makes sense too. > > In general there seems to be an agreement, so it would be great to document > in some place. Many years will pass before we have another "special" release > like Python 2.7, so it's worth spending an extra few minutes to have this > written

Re: [python-committers] hg clone cpython newrepo aborts

2013/5/28 Senthil Kumaran : > > On Tue, May 28, 2013 at 7:19 AM, Dirkjan Ochtman wrote: >> >> On Tue, May 28, 2013 at 4:11 PM, Senthil Kumaran >> wrote: >> > While trying to clone a cpython repo to a new repo. I am getting this >> > error. >> > >> > getting Lib/idlelib/idle.bat >> > getting Lib/i

Re: [python-committers] what's going on with Misc/NEWS?

2013/5/24 Brett Cannon : > It's an extreme example, but for instance I added an entry for this > sys.modules change where I just added a clarifying sentence. Probably > not needed but wanted to make sure that people got the message they > shouldn't replace sys.modules. Does anybody actually ready

[python-committers] 2.7.4rc1 tagged

The 2.7.4rc1 tag is in the main hg repo. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Branches support status (Re: 3.3 branch created in main repository)

2012/10/1 Georg Brandl : > I've now added lifespan information to the 3.2 and 3.3 release schedule > PEPs, perhaps Barry and Benjamin could do the same for 2.6 to 3.1. I just updated the 3.1 and 2.7 schedules. -- Regards, Benjamin ___ python-committer

Re: [python-committers] 3.3.1 two months away?

2012/10/1 R. David Murray : > On the other hand, Gentoo (Arfrever) already found one crasher > post-release...but fortunately it only happens in debug builds (although > that could mean there is a behavior bug in non-debug builds). It definitely happens in release builds. -- Regards, Benjamin _

Re: [python-committers] Branches support status (Re: 3.3 branch created in main repository)

2012/9/30 Jesus Cea : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 29/09/12 10:35, Georg Brandl wrote: >> Until the last ordinary 3.2 bugfix release is done (which will be >> soon), the usual procedure for 3.x will be to check into 3.2, merge >> into 3.3, and then merge into default, ex

Re: [python-committers] Cutting 3.3 branch now. Why not?

2012/6/28 Jesus Cea : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Python 3.3 is currently in beta, so the rythm of new patches in > "default" will decrease and people with new features MUST wait until > 3.3 is out. I think this is a waste of time. And even if people is > working with HG p

Re: [python-committers] state of repo?

2012/4/5 R. David Murray : > I just tried to merge a change from 3.2 to default and found an unexpected > file being merged.  Looking at the graph, it *looks* like Sandro copied a > change to default instead of merging it, even though his commit comment > says merge.  That would be fine, I'd just d

Re: [python-committers] Time to cut new rc2 release candidates - expat DoS fix is in

2012/3/15 Barry Warsaw : > On Mar 15, 2012, at 08:32 AM, Georg Brandl wrote: > >>Thanks.  I will do the tagging and packaging on Saturday. > > I'll do the same for 2.6. I'm traveling this weekend, so I'll probably tag today or tomorrow. -- Regards, Benjamin _

Re: [python-committers] Time to cut new rc2 release candidates - expat DoS fix is in

2012/3/14 Gregory P. Smith : > The fixes for the expat hash randomization DoS are in and working - > http://bugs.python.org/issue14234.  New stable and security fix rc2 release > candidates should be created for 2.6, 2.7, 3.1 and 3.2. Okay. Can you tell me the commits I need to transplant to the 2

Re: [python-committers] security and bugfix releases tagged

2012/2/25 "Martin v. Löwis" : >>> Am 24.02.2012 17:49, schrieb Benjamin Peterson: >>>> Hi Ned and Martin, >>>> 2.7.3rc1 and 3.2.3rc1 are tagged in the repo ready for binaries. >>> >>>  1b605fb13977c887a9554a9896b8  16081986  

Re: [python-committers] security and bugfix releases tagged

Thank you. Do you want to add signatures? 2012/2/24 "Martin v. Löwis" : > Am 24.02.2012 17:49, schrieb Benjamin Peterson: >> Hi Ned and Martin, >> 2.7.3rc1 and 3.2.3rc1 are tagged in the repo ready for binaries. > >  1b605fb13977c887a9554a9896b8  16

[python-committers] security and bugfix releases tagged

Hi Ned and Martin, 2.7.3rc1 and 3.2.3rc1 are tagged in the repo ready for binaries. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] 3.2 branch in mercurial

2012/1/4 Senthil Kumaran : > I think, there is something wrong with state of hg.python.org at the moment. > > On a fresh clone from hg.python.org > > $hg clone ssh://h...@hg.python.org/cpython cpython > > If I do, hg branches, the 3.2 is shown as inactive. Did something > change recently? It just

Re: [python-committers] Pulling from contributors repositories

2011/6/12 Ned Deily : > There are several ways we could eliminate this needless pain.  Probably > the simplest would be to agree on a simple format for including the NEWS > and ACK info in the hg commit message and then agree on a process to > batch update the NEWS and ACK files from the commit mes

[python-committers] 2.7.2 and 3.1.4 tagged

Hi, 2.7.2 and 3.1.4 have been tagged (in the main repo) and are ready for binary building. Thanks, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] state of the 3.2 branch

2011/6/8 R. David Murray : > I am completely confused by the state of the 3.2 branch.  My understanding > is that RC1 has been released, that RC2 is coming soon, and that Georg > is releasing 3.2.1 from a separate clone so that we do not have to have > a freeze in the main repo.  All that is fine,

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

2011/5/31 "Martin v. Löwis" : > Am 30.05.2011 23:36, schrieb Benjamin Peterson: >> 2011/5/30 Victor Stinner : >>> Le dimanche 29 mai 2011 22:55:17, Benjamin Peterson a écrit : >>>> Hi, >>>> I'm going to start spinning those releases now. I&

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

2011/5/30 Victor Stinner : > Le dimanche 29 mai 2011 22:55:17, Benjamin Peterson a écrit : >> Hi, >> I'm going to start spinning those releases now. I'll make a branch for >> 2.7.2 but not for 3.1.4. Please stop committing to 3.1; it's going >> into secu

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

2011/5/29 Victor Stinner : > Le dimanche 29 mai 2011 22:55:17, Benjamin Peterson a écrit : >> Hi, >> I'm going to start spinning those releases now. I'll make a branch for >> 2.7.2 but not for 3.1.4. Please stop committing to 3.1; it's going >> into se

[python-committers] 2.7.2 and 3.1.4 rc now

Hi, I'm going to start spinning those releases now. I'll make a branch for 2.7.2 but not for 3.1.4. Please stop committing to 3.1; it's going into security only mode. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org h

Re: [python-committers] Committer rights for Nadeem Vawda

2011/4/7 Jesus Cea : > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 07/04/11 22:41, Antoine Pitrou wrote: >> Le jeudi 07 avril 2011 à 10:27 -0700, Brett Cannon a écrit : >>> The devguide knows all: http://docs.python.org/devguide/coredev.html >> >> Hmmm so I assume Nadeem should send his

Re: [python-committers] branches are open

2011/2/21 Georg Brandl : > py3k is now 3.3a0, and I've created a new release32-maint branch. > Thanks to Martin for setting up svnmerge on the new branch; please > merge all bug fixes to release32-maint as usual. > > Benjamin, how long will you want to maintain 3.1 in bugfix mode? I will try to re

Re: [python-committers] Blocking feature backports

2010/12/1 Terry Reedy : > I would like to commit a couple of new feature patches in the next couple of > days for #9299 (if no one else does it) and #10534 (working on that).  It > appears to be somewhat customary to follow such patches with 3.1/2.7 blocks, > but Georg implied in another message th

[python-committers] 2.7.* and 3.1.* branches open

With 2.7.1 and 3.1.3 out, the maintenance branches are again open. I would expect 3.1.4 and 2.7.2 to be released in the June/July area. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/l

[python-committers] 2.7.1 and 3.1.3 today

I'm going to start working on the releases now, so the maintenance branches are now closed. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] maintenance branches are open

2010/11/20 Éric Araujo : >> 2.7.1rc1 and 3.1.3rc1 are released, so their branches are open now. >> Please only very safe bug fixes until final (two weeks). > > I’m afraid I can’t define what a very safe fix is.  I think I won’t > merge anything for another week and then suffer the pains of svnmerge

[python-committers] maintenance branches are open

2.7.1rc1 and 3.1.3rc1 are released, so their branches are open now. Please only very safe bug fixes until final (two weeks). -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/pyt

[python-committers] 2.7 and 3.1 branches frozen for RC

All branches are closed now. I'll be on #python-dev and on email if you need me. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Deny nonbreaking spaces in the precommit script?

2010/11/8 Łukasz Langa : > Am 07.11.2010 19:28, schrieb Benjamin Peterson: >> >> 2010/11/7 Victor Stinner: >>> >>> I would like to know if it would be >>> possible to block a commit introducing nonbreaking spaces? A least for me >>> :-)

Re: [python-committers] Deny nonbreaking spaces in the precommit script?

2010/11/7 Victor Stinner : > Hi, > > I introduced nonbreaking spaces in Lib/os.py in a comment, because I kept Alt > Gr. key pressed to write the space after # (stupid Xorg keyboard variant!). > > This change introduces a strange bug in "LANG=C ./python -m test.regrtest -v > test_imp test_trace" co

Re: [python-committers] JetBrains PyCharm license for the team

2010/10/22 Georg Brandl : > Am 22.10.2010 20:53, schrieb Brett Cannon: >> On Fri, Oct 22, 2010 at 10:53, Georg Brandl wrote: >>> Am 22.10.2010 19:33, schrieb Brett Cannon: JetBrains has granted us a group FLOSS license for PyCharm: http://www.jetbrains.com/pycharm/ . It's good for a year

Re: [python-committers] PEP checkin process

2010/7/22 Nick Coghlan : > On Thu, Jul 22, 2010 at 6:35 PM, Barry Warsaw wrote: >> On Jul 22, 2010, at 08:17 AM, Nick Coghlan wrote: >> >>>Useful commands (using PEP 3150 as my example): >>>python genpepindex.py # ./genpepindex.py only works if Python 2.5 is >>>installed ./pep2html.py -b 3150 # Ge

Re: [python-committers] PEP checkin process

2010/7/21 Nick Coghlan : > On Thu, Jul 22, 2010 at 2:15 AM, Guido van Rossum wrote: >> You can check in directly. The peps@ list is only for PEP authors >> without checkin privileges, or if you're not sure you have conformed >> to the PEP template sufficiently well. Picking a PEP number is >> arbi

Re: [python-committers] 2.7 almost out the door

2010/7/3 Alexander Belopolsky : > The "What’s New in Python 2.7" document says "Python 2.7 was released > on July 7, 2010."  Is this a typo or you plan a 4-day cool off period > before making an announcement? I was thinking of July being the 7th month when I did that. -- Regards, Benjamin _

[python-committers] 2.7 almost out the door

2.7 has been tagged, and I have uploaded docs and the source tarballs to python.org. I will wait on binaries before announcing the release. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailm

[python-committers] churning 2.7

The last release blockers have been closed, so I'm now going to go ahead if the release. Please no commits to the trunk... ever again! :) -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman

[python-committers] changes after 2.7 final

After I tag 2.7 this Saturday, I will effect the following changes in the repository: - I will make the 2.7 maintenance branch. - I will remove svnmerge from trunk -> py3k. - I will initialize svnmerge from py3k -> 2.7maint. - The trunk will be officially closed. I suggest you just delete your trun

Re: [python-committers] Delaying 3.2 release

2010/6/30 Georg Brandl : > All in all, hearing the arguments in this thread I agree that a month > more time for development is a good thing, and I will update the release > schedule accordingly. You could just throw in another alpha. It never hurts to get the code out there IMO. -- Regards, Be

[python-committers] trunk open

The final release is next, so there really should be excellent reasons to change things in the trunk now. -- Regards, Benjamin ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

  1   2   >