Re: [python-committers] Promote Xavier de Gaye as a core developer

On 05/20/2016 10:53 PM, Victor Stinner wrote: > Hi, > > I propose to promote Xavier de Gaye as a Python core developer. > > I noticed that he is proposing good patches since a lot time ago > (first one around 2010! issue #9250). He now looks to be motivated to > help porting CPython to Android. I

Re: [python-committers] Making the PSF CoC apply to core developers

On 03/05/2016 01:07 AM, Brett Cannon wrote: > > > On Fri, 4 Mar 2016 at 15:07 R. David Murray > wrote: > > On Fri, 04 Mar 2016 21:31:44 +, Brett Cannon > wrote: > > The discussion about the Code of Conduct has sputtered out

Re: [python-committers] Making the PSF CoC apply to core developers

On 02/28/2016 10:25 PM, Brett Cannon wrote: > > > On Sun, Feb 28, 2016, 12:02 Georg Brandl <mailto:g.bra...@gmx.net>> wrote: > > On 02/28/2016 08:10 PM, Brett Cannon wrote: > > > Can *anyone* take it upon themselves to (let's > >

Re: [python-committers] Making the PSF CoC apply to core developers

On 02/28/2016 08:10 PM, Brett Cannon wrote: > Can *anyone* take it upon themselves to (let's > say) say "Brett, you unilaterally changed the policy with no discussion > or consultation and just four minutes notice. That is unspeakably rude > and total jerk behaviour, so under your

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

This is now a moot point, but with generaldelta (active by default in hg 3.7) the hg clone size is at around 400 MB. Georg On 01/04/2016 11:53 PM, Alex Gaynor wrote: > My git clone is 350MB (after a make clean), a fresh hg clone is 650MB. > > Alex > > On Mon, Jan 4, 2016 at

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

On 01/01/2016 08:24 PM, 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 decision or help with the transition, please > subscribe to the core-workflow maili

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

On 10/02/2015 09:21 AM, Nick Coghlan wrote: > On 2 October 2015 at 15:33, Benjamin Peterson wrote: >> 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, problem

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

Hi all, newer OpenSSH versions (7.0+) default to not allowing ssh-dss keys for public key authentication. If you experience "permission denied" errors, this (currently) comes from the client side only and hg.python.org will accept these keys if you enable them using the PubkeyAcceptedKeyTypes opt

Re: [python-committers] Proposed core developer for contributing to multiprocessing

On 01/10/2015 12:03 AM, M.-A. Lemburg wrote: >>> Antoine and Victor argued that new developers should first >>> show their skills by submitting patches to tickets, working >>> with other core devs before getting the commit bit set. >>> >>> My suggestion was allowing new developers to start committ

[python-committers] [RELEASED] Python 3.2.6, Python 3.3.6

These are production versions, please report any bugs to http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and contributors) -BEGIN PGP SIGNATURE- Version: GnuPG v2 iEYEARECAAYF

Re: [python-committers] [RELEASE] Python 3.4.2 is now available

On 10/08/2014 08:39 PM, Terry Reedy wrote: > On 10/8/2014 4:57 AM, Larry Hastings wrote: >> >> >> On behalf of the Python development community and the Python 3.4 release >> team, I'm pleased to announce the availability of Python 3.4.2. Python >> 3.4.2 has many bugfixes and other small improvement

Re: [python-committers] Anatoly (again)

On 10/06/2014 02:56 PM, Nick Coghlan wrote: > Why is Anatoly posting to python-dev? I thought he was banned when he was > banned > from the tracker. > > I refuse to waste my time trying to reason with him, and I consider the "just > ignore him" approach to be unacceptable, as it leaves him free t

Re: [python-committers] Mark Lawrence

On 10/05/2014 11:01 PM, Ned Deily wrote: > In article , > Georg Brandl wrote: >> On 10/05/2014 09:36 PM, Ned Deily wrote: >> > To me, the main issue is that the noise is not just directed at python >> > committers but also to the python users who have submitted

Re: [python-committers] Mark Lawrence

On 10/05/2014 09:36 PM, Ned Deily wrote: > On Oct 5, 2014, at 12:24 , R. David Murray wrote: >> >> It is certainly true that I for one ignore anything with his name on it, >> because most of the time it is noise and it isn't worth the effort to >> figure out which ones aren't noise. > > To me,

[python-committers] [RELEASED] Python 3.2.6rc1, Python 3.3.6rc1

https://www.python.org/downloads/release/python-336rc1/ These are pre-releases, please report any bugs to http://bugs.python.org/ The final releases are scheduled one week from now. Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and contrib

Re: [python-committers] 3.2.6, 3.3.6 planned for weekend

If you mean https://hg.python.org/cpython/rev/9e765e65e5cb, then yes: it was already on 3.3, and I ported it to 3.2 among other fixes today. cheers, Georg On 09/30/2014 05:35 PM, Guido van Rossum wrote: > Did the cookie fix get ported to these? > > On Sep 30, 2014 5:50 AM, &quo

[python-committers] 3.2.6, 3.3.6 planned for weekend

Hi all, I'm planning to tag 3.2 and 3.3 branch security releases on the weekend. No binary packages will need to be produced. Please let me know if there is any security-level fix you'd want to fit in before. cheers, Georg ___ python-committers mailin

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

Am 17.03.2014 22:36, schrieb Victor Stinner: > Hi, > > I modified the Misc/NEWS file: > > * I moved 3.3 sections to Misc/HISTORY: items were already present, > but the format in Misc/NEWS was improved (changeset 6ba468d4fa96) > * I removed 3.4.1 section: changes of 3.4 after 3.4.0 must already be

[python-committers] 3.3 branch is now in security fix mode

Hi all, since 3.3.5 and 3.4.0 practically coincided, it is a good point to end the bugfix maintenance of the 3.3 branch. Please only commit security-related fixes to 3.3 from now -- like for 3.2 -- and as always, please set tracker issues that relate to security fixes to "release blocker" priorit

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

Am 17.03.2014 17:37, schrieb "Martin v. Löwis": > Am 17.03.14 16:18, schrieb Benjamin Peterson: >> >> >> 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

[python-committers] [RELEASED] Python 3.3.5

3.3.5 visit: http://www.python.org/downloads/release/python-335/ This is a production release, please report any bugs to http://bugs.python.org/ The final release is scheduled one week from now. Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire p

[python-committers] [RELEASED] Python 3.3.5 release candidate 2

nload Python 3.3.5 visit: http://www.python.org/download/releases/3.3.5/ This is a preview release, please report any bugs to http://bugs.python.org/ The final release is scheduled one week from now. Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire p

[python-committers] [RELEASED] Python 3.3.5 release candidate 1

nload Python 3.3.5 visit: http://www.python.org/download/releases/3.3.5/ This is a preview release, please report any bugs to http://bugs.python.org/ The final release is scheduled one week from now. Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire p

Re: [python-committers] RC phase?

Am 13.02.2014 14:15, schrieb Antoine Pitrou: > > Hello, > > So how is the RC phase supposed to work this time? Usually only critical > patches get in, but I see a lot of commits in the last few days. For 3.3.0 bugfixing continued on default, and I cherry-picked patches I considered critical enou

[python-committers] [RELEASED] Python 3.3.4

http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.3's contributors) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlL5PMwACgkQN9GcIYhpnLCv4wCePNVqwsOYCHdJBi

[python-committers] [RELEASED] Python 3.3.4 release candidate 1

http://www.python.org/download/releases/3.3.4/ This is a preview release, please report any bugs to http://bugs.python.org/ The final version is scheduled to be released in two weeks' time, on or about the 10th of February. Enjoy! - -- Georg Brandl, Release Manager georg at pyth

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

Am 17.01.2014 06:34, schrieb Benjamin Peterson: > 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

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

Am 17.01.2014 00:57, schrieb Nick Coghlan: > > On 17 Jan 2014 03:25, "Serhiy Storchaka" <mailto:storch...@gmail.com>> wrote: >> >> четвер, 16-січ-2014 15:03:28 Georg Brandl написано: >> > Am 16.01.2014 14:47, schrieb Antoine Pitrou: >>

[python-committers] 3.3.4 planning

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, probably in the May-June timeframe. cheers, Georg ___

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

Am 16.01.2014 14:47, schrieb Antoine Pitrou: > On jeu., 2014-01-16 at 14:22 +0100, Georg Brandl wrote: >> 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 >> >> Oh, only once or twic

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 Oh, only once or twice for every 3.x release so far :) > but anyway: > > Why not branch 3.4 earlier than release? That is how big projects are managed > nowadays, you

Re: [python-committers] clinic churn after beta2

Am 08.01.2014 11:08, schrieb Nick Coghlan: > > On 8 Jan 2014 17:06, "Georg Brandl" <mailto:g.bra...@gmx.net>> > wrote: >> >> Am 08.01.2014 03:23, schrieb Benjamin Peterson: >> > On Tue, Jan 7, 2014, at 06:06 PM, Nick Coghlan wrote: >

Re: [python-committers] clinic churn after beta2

Am 08.01.2014 03:23, schrieb Benjamin Peterson: > 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

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

Am 01.12.2013 03:12, schrieb Nick Coghlan: > On 1 December 2013 01:49, Eli Bendersky wrote: >> On Fri, Nov 29, 2013 at 11:44 PM, Nick Coghlan wrote: >>> OK, moving on to mechanics, here's what I would like to propose: >>> >>> - flip his moderation bit on the mailing lists, at least for >>> python

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

Am 29.11.2013 19:22, schrieb Tim Peters: > I pretty much ignore Anatoly, and that works really well for me - try it ;-) > It's a nice option, I agree -- but someone has to triage his issues, or they will rot in the tracker for eternity. Georg ___ pyth

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. There's no reason for banning - he

[python-committers] [RELEASED] Python 3.3.3 final

visit: http://www.python.org/download/releases/3.3.3/ This is a production release, please report any bugs to http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.3's contributors) [1] http://bugs.

[python-committers] [RELEASED] Python 3.3.3 release candidate 2

gs to http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.3's contributors) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlKB1G4ACgkQN9GcIYhpnLAu5gCfRkfpnEs+rmtZ9i

[python-committers] [RELEASED] Python 3.3.3 release candidate 1

to be released in two weeks' time, on or about the 10th of November. Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and 3.3's contributors) -BEGIN PGP SIGNATURE- Version: GnuPG v2.

Re: [python-committers] 3.3.3rc1 tagged

Am 27.10.2013 13:57, schrieb Georg Brandl: > Hi, > > I've tagged 3.3.3rc1 today; final is scheduled for Nov 8. Please notify > me of any 3.3 regressions you find; I will then port them to the repo > from which the final is cut. > > General bugfixing can continue on

[python-committers] 3.3.3rc1 tagged

Hi, I've tagged 3.3.3rc1 today; final is scheduled for Nov 8. Please notify me of any 3.3 regressions you find; I will then port them to the repo from which the final is cut. General bugfixing can continue on the 3.3 branch in the main repo and will not be relevant for 3.3. cheers, Georg _

Re: [python-committers] 3.2 -> 3.3 merge pending?

On 05/29/2013 10:27 PM, Senthil Kumaran wrote: > > On Wed, May 29, 2013 at 7:41 AM, R. David Murray > wrote: > > > I asked about this on IRC and was told that 3.2 is now a standalone branch > like 2.7. Security fixes will be applied by the release manager

[python-committers] [RELEASED] Python 3.2.5 and Python 3.3.2

report bugs to http://bugs.python.org/ (Thank you to those who reported these regressions.) Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and all contributors) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux

[python-committers] [RELEASED] Python 3.2.4 and Python 3.3.1

://www.python.org/download/releases/3.3.1/ respectively. As always, please report bugs to http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and all contributors) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU

Re: [python-committers] Please don't commit to 3.2 branch anymore

On 03/31/2013 06:27 PM, Vinay Sajip wrote: > Georg Brandl gmx.net> writes: > >> with 3.2.4 being the last regular 3.2 maintenance release and the rc out >> of the door, the 3.2 branch should only be committed to for security >> releases. So please don't commit

Re: [python-committers] Please don't commit to 3.2 branch anymore

On 03/30/2013 06:14 PM, Antoine Pitrou wrote: > Le samedi 30 mars 2013 à 10:13 -0700, Ned Deily a écrit : >> In article <20130330141534.44893250...@webabinitio.net>, >> "R. David Murray" wrote: >> > This is the first time we've been in the situation of having a >> > security-only branch in Mercur

Re: [python-committers] Please don't commit to 3.2 branch anymore

On 03/30/2013 04:20 PM, Jesus Cea wrote: > On 30/03/13 16:10, Jesus Cea wrote: >> Something simple would be for the hook to refuse any commit in >> that branch UNLESS it is coming from the maintainer. > > BTW, are the hooks available anywhere. I am interested in the "create > patch" hook and the "

Re: [python-committers] Please don't commit to 3.2 branch anymore

On 03/30/2013 04:10 PM, Jesus Cea wrote: > On 30/03/13 15:15, R. David Murray wrote: >> This is the first time we've been in the situation of having a >> security-only branch in Mercurial (other than 2.7, which is its own >> head). So I don't believe we have articulated a procedure yet. > > I am a

[python-committers] Please don't commit to 3.2 branch anymore

Hi all, with 3.2.4 being the last regular 3.2 maintenance release and the rc out of the door, the 3.2 branch should only be committed to for security releases. So please don't commit anything there anymore. To help everyone remember, I've configured the push hook to reject changesets to the 3.2

[python-committers] [RELEASED] Python 3.2.4 rc 1 and Python 3.3.1 rc 1

notice to: http://bugs.python.org/ To download Python 3.2.4 or Python 3.3.1, visit: http://www.python.org/download/releases/3.2.4/ or http://www.python.org/download/releases/3.3.1/ respectively. Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire

Re: [python-committers] Tracker settings for Peter Moody

Am 16.03.2013 15:01, schrieb Nick Coghlan: > Could someone with sufficient privileges please flip Peter Moody's > commit bit in the tracker: http://bugs.python.org/user9293 Done. > Reminder to everyone else: if you have commit privileges, but don't > have the Python logo showing up next to your

Re: [python-committers] server-side clones for deletion

Am 09.01.2013 10:30, schrieb Antoine Pitrou: > > Hi, > >> I was testing whether Rietveld could be used to review a devguide >> patch, and I accidentally created this server-side clone: >> >> http://hg.python.org/cjerdonek/sandbox-devguide/ >> >> Is there a way for me to remove it, or does someone

Re: [python-committers] server-side clones for deletion

Am 09.01.2013 10:06, schrieb Chris Jerdonek: > I was testing whether Rietveld could be used to review a devguide > patch, and I accidentally created this server-side clone: > > http://hg.python.org/cjerdonek/sandbox-devguide/ > > Is there a way for me to remove it, or does someone else need to do

Re: [python-committers] server-side clones for deletion

Am 09.01.2013 11:50, schrieb Victor Stinner: > I also have various old repositories. Could you please remove the 2 > following repositories? > > features/faster-format: work merged into cpython, issues #14716 and #14744 > sandbox/split-unicodeobject.c: idea rejected after two discussions on > pyth

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

On 01/01/2013 11:13 PM, Ezio Melotti wrote: > Hi, > > On Tue, Jan 1, 2013 at 11:55 PM, Brian Curtin wrote: >> On Tue, Jan 1, 2013 at 3:49 PM, Ezio Melotti wrote: >>> Hi, >>> >>> On Tue, Jan 1, 2013 at 10:57 PM, Georg Brandl wrote: >&

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

On 01/01/2013 05:54 PM, Ezio Melotti wrote: > I say Ezio lets him know that this is the plan since he talked to him > recently and is in the no-ban-yet camp. > > > Yesterday I talked to him, informed him about the probation and showed him > this > message. I hope this is official enoug

Re: [python-committers] privacy

On 12/26/2012 06:17 PM, Eli Bendersky wrote: > > At the risk of stating something that I imagine everyone already > > knows, this list is itself publicly viewable: > > > > http://mail.python.org/mailman/listinfo/python-committers > > > > So in some s

Re: [python-committers] Commit privs for Serhiy Storchaka?

The SSH key is added; tracker privileges were already given. Welcome Serhiy! Georg On 12/26/2012 05:02 PM, Andrew Svetlov wrote: > Ok. Thanks. > > Sent to Serhiy link to instructions for next steps > (http://docs.python.org/devguide/coredev.html#gaining-commit-privileges) > as Nick suggested. >

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

FWIW, I agree 100% with Terry here. I'm certainly annoyed by many of Anatoly's contributions, and find myself extremely unwilling to do anything about his perceived issues, but to exclude a community member publicly (!) from all (!) python.org resources is going too far IMO. Individual policy vio

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

On 10/02/2012 11:47 AM, Victor Stinner wrote: So, if I understand correctly, the current situation is this: 2.6: Security fixes only 2.7, 3.2, 3.3: Bugfixes only 2.3, 2.4, 2.5, 3.0, 3.1: Dead Would it be possible to write this status in the devguide (and also maintain it!)? I would support p

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

On 10/02/2012 02:37 AM, Jesus Cea wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/10/12 02:25, R. David Murray wrote: 3.3 will receive bugfix updates approximately every 4-6 months until one release after the release of 3.4.0 final. After that, security [...] As a native English s

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

On 10/01/2012 07:30 PM, Benjamin Peterson wrote: 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 happe

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

On 10/01/2012 04:57 PM, Terry Reedy wrote: On 10/1/2012 1:02 AM, Georg Brandl wrote: You are right that we should have information about bugfix/security mode and about end-of-life; I propose to put them in the respective release schedule PEPs. From the commit: > +3.3 will receive bug

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

On 10/01/2012 01:30 PM, "Martin v. Löwis" wrote: Is there a PEP with end-of-life info? I had meant to write a PEP on security releases for several years now. Since this still doesn't exist, here is the outline of the procedures that maintainers have agreed upon: - bug fix releases are made unti

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

On 10/01/2012 04:29 AM, Jesus Cea wrote: -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

[python-committers] 3.3 branch created in main repository

Hi all, from now on there is a 3.3 branch in the main repo. 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, except of course for a) fixes of 3.3-only features and b) trivi

Re: [python-committers] Alexander Belopolsky

On 09/21/2012 02:54 AM, Jesus Cea wrote: > Alexander Belopolsky is a core developer but the bugtracker doesn't > have a "contributor form received" flag for him? > > An oversight?. Can anybody check the forms and change the flag? > > Check: May I not

Re: [python-committers] Commit privileges for Chris Jerdonek

On 09/23/2012 07:23 PM, Mark Dickinson wrote: > On Sun, Sep 23, 2012 at 6:20 PM, Ezio Melotti wrote: >> Hi, >> I would like to propose Chris Jerdonek as a new core developer. > > +1 +1 Georg ___ python-committers mailing list python-committers@pytho

[python-committers] 3.3 rc2 released

Hi, quite a few critical changes went into rc2; thanks to everyone for helping fix these issues. If possible in any way, I'd like to cut down the number of changes between the last rc and the final to zero. That means that any nontrivial changes in rc2 will lead to a third rc. Georg __

Re: [python-committers] Committer metadata not updating?

On 09.09.2012 09:14, Georg Brandl wrote: > On 09.09.2012 05:01, Nick Coghlan wrote: >> I just noticed that Eric Snow wasn't showing up as a committer on the >> tracker, even though I've seen him push the PEP 421 updates to the 3.3 >> What's New docs

Re: [python-committers] Committer metadata not updating?

On 09.09.2012 05:01, Nick Coghlan wrote: > I just noticed that Eric Snow wasn't showing up as a committer on the > tracker, even though I've seen him push the PEP 421 updates to the 3.3 > What's New docs. > > He's also missing from http://www.python.org/dev/committers and > http://docs.python.org/

[python-committers] Reminder: 3.3.0 commits only on release clone

Hi, 3.3.0 rc1 is now out, and I'd like to remind you that commits you want to be in 3.3.0 rc2 or final have to be in my release clone, so you need to tell me you want them there. Either ping me on IRC, or send an email, and I'll have a look. cheers, Georg __

Re: [python-committers] 3.3 rc1 next week

Well, I can certainly push the branch back to the main repo, but I really don't want anyone else committing to it. Georg On 21.08.2012 00:05, Victor Stinner wrote: Why not creating a 3.3.0 branch to prepare the release instead of a different repository? Victor Le 19 août 2012 13:05, &

[python-committers] 3.3 rc1 next week

Dear committers, if the buffer/array-related blockers are resolved in time, the rc1 will be released one week from now. Since some people asked: at the moment we are not in the RC phase yet, so fixing bugs is allowed, but it would be advisable to have a second committer review any nontrivial fix

[python-committers] 3.3beta2 delayed

Hi all, as you might have noticed, a couple of blocker-level bugs have crept up that delayed the beta2 release again. I want these fixed before beta2 is done, which might take another week. In any case, please don't be too adventurous with your bugfixes :) Georg ___

[python-committers] 3.3 schedule

Hi, due to the extensive fixes done in pkgutil/importlib, I've postponed the beta2 and with it the following releases by one week. I.e., the beta2 will be released on or shortly after July 21. Georg ___ python-committers mailing list python-committers

Re: [python-committers] PEP regeneration on the website

On 16.07.2012 15:43, Antoine Pitrou wrote: > Le lundi 16 juillet 2012 à 23:26 +1000, Nick Coghlan a écrit : >> I just noticed that PEP 424 hasn't appeared on the site yet - is it >> possible the automatic regeneration broke when hg.python.org was moved >> to OSU/OSL? > > Yes, it appears to have br

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

On 29.06.2012 02:23, Jesus Cea wrote: -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

[python-committers] Alpha 4 tomorrow

Hi all, it has been requested to delay a4 a bit more, so I will tag tomorrow either afternoon or evening UTC. It's just another alpha after all, so there is no rush to get in features yet (and I hope there won't be before beta either). Georg ___ pytho

Re: [python-committers] state of repo?

Am 06.04.2012 04:44, schrieb 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

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

On 15.03.2012 02:39, Gregory P. Smith wrote: On Wed, Mar 14, 2012 at 6:35 PM, Benjamin Peterson mailto:benja...@python.org>> wrote: 2012/3/14 Gregory P. Smith mailto:g...@krypto.org>>: > The fixes for the expat hash randomization DoS are in and working - > http://bugs.python.org/

Re: [python-committers] Language summit

On 09.03.2012 09:04, Brian Curtin wrote: On Mar 8, 2012 10:32 PM, "Georg Brandl" mailto:g.bra...@gmx.net>> wrote: > > Will we poor non-attendants get some minutes of what was discussed? > > Thanks, > Georg I plan to take Senthil's, Eric Snow's,

[python-committers] Language summit

Will we poor non-attendants get some minutes of what was discussed? Thanks, Georg ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

[python-committers] Working on 3.3.0a1

Hi all, as planned in PEP 398, the first alpha of Python 3.3.0 will be released this weekend. I'll cut the tag today, and I assume binaries will follow in the course of next week. cheers, Georg ___ python-committers mailing list python-committers@pyt

Re: [python-committers] Tagging release candidates, fixing issue 13704

Am 23.02.2012 16:48, schrieb Barry Warsaw: > Quick note: Benjamin and I are going to tag our respective branches for > release candidates fixing the hash security issue. Haven't heard from Georg > yet, but I think we'll wait on the actual rc releases until he's had a chance > to tag his branches t

Re: [python-committers] Including bugfix releases in schedule PEPs

Am 05.02.2012 13:52, schrieb Éric Araujo: > Hi, > > I’m often wondering when the new bugfix releases will take place, to > know how much time I have to fix some critical bugs. The “Python X.Y > release schedule” PEPs stop at the X.Yf0 release. Would it be a good > idea if release managers update

[python-committers] 3-way conflict markers

Hi, for those of you who also miss the seeing base revision in merge conflict markers sometimes, I recently saw this post on mercurial-devel: http://comments.gmane.org/gmane.comp.version-control.mercurial.devel/45022 There is a reason why it is not the default behavior: mercurial collapses confl

Re: [python-committers] Three wishes for Mercurial-Roundup integration

Am 12.10.2011 18:10, schrieb Éric Araujo: > Le 06/10/2011 19:25, Georg Brandl a écrit : >> Did you get a "sent email to roundup" message on push? > > Just pushed to the distutils2 repo: > > remote: adding changesets > remote: adding manifests > remote:

Re: [python-committers] Three wishes for Mercurial-Roundup integration

On 10/06/11 16:34, Éric Araujo wrote: > Le 03/09/2011 08:42, Georg Brandl a écrit : >> Am 02.09.2011 18:53, schrieb Éric Araujo: >>>>> 3) To let us track the backport of changesets from cpython/packaging to >>>>> distutils2, I would like the script to loo

Re: [python-committers] Request email from buildbot when forcing a build?

Am 18.09.2011 14:35, schrieb Nick Coghlan: > Q for the buildbot admins: would it be easy to add an "Email Address" > field to the 'Force Build' form, so buildbot could email me when the > job was complete? > > This doesn't come up very often, and would just be a nice to have, so > don't worry abou

Re: [python-committers] Commit rights for Meador Inge

Am 14.09.2011 22:46, schrieb Mark Dickinson: > Hi all, > > Meador Inge has been contributing to Python for a while now; he's put > in a lot of work in particular on the struct and ctypes modules > amongst others (see username 'meadori' in the tracker for more), and > all the work that I've seen h

[python-committers] [RELEASED] Python 3.2.2

list of changes in 3.2, see http://docs.python.org/3.2/whatsnew/3.2.html To download Python 3.2 visit: http://www.python.org/download/releases/3.2/ Please consider trying Python 3.2 with your code and reporting any bugs you may notice to: http://bugs.python.org/ Enjoy! - -- Georg

[python-committers] Working on 3.2.2

I've now pulled all 3.2 changes that I think are important and safe into the release clone and am working on making the tag. Georg ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo/python-committers

Re: [python-committers] Three wishes for Mercurial-Roundup integration

Am 02.09.2011 18:53, schrieb Éric Araujo: >>> 3) To let us track the backport of changesets from cpython/packaging to >>> distutils2, I would like the script to look at changesets in the >>> distutils2 repo and send messages to Roundup when a bug number is detected. >> Sure. Should be a simple [h

Re: [python-committers] Three wishes for Mercurial-Roundup integration

Am 31.08.2011 16:39, schrieb Éric Araujo: > Hi, > > 1) When a commit message references more than one bug (with text > matching #\d+), only the first gets a message for the changeset. I > would like all referenced bugs to get a message. +1. Just make sure that only issues that should be closed

[python-committers] 3.2.2 delayed

Due to other deadlines, I have to delay 3.2.2 final to the coming weekend. Nothing much changes for most of you, just if you were wondering... Georg ___ python-committers mailing list python-committers@python.org http://mail.python.org/mailman/listinfo

[python-committers] Working on 3.2.2rc1

I've created another release clone for 3.2.2rc1 and am working on that release now. There are consistent failures in test_distutils on the Windows machines; it would be nice to get these fixed. If anyone can do that in the next few hours, please tell me on #python-dev, otherwise it'll have to wai

[python-committers] [RELEASED] Python 3.2.1

features in the 3.2 line, see http://docs.python.org/3.2/whatsnew/3.2.html To download Python 3.2.1 visit: http://www.python.org/download/releases/3.2.1/ This is a final release: Please report any bugs you may notice to: http://bugs.python.org/ Enjoy! - -- Georg Brandl, Release

Re: [python-committers] Mercurial upgrade

Am 05.07.2011 04:08, schrieb Jesus Cea: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 04/07/11 21:01, Antoine Pitrou wrote: >> I've upgraded the Mercurial version on hg.python.org to 1.9. Also, >> I've enabled the experimental "generaldelta" repository feature on >> the server, which m

Re: [python-committers] Mercurial upgrade

Am 04.07.2011 23:03, schrieb Antoine Pitrou: > > Le lundi 04 juillet 2011 à 22:51 +0200, Dirkjan Ochtman a écrit : >> On Mon, Jul 4, 2011 at 21:01, Antoine Pitrou wrote: >> > I've upgraded the Mercurial version on hg.python.org to 1.9. >> > Also, I've enabled the experimental "generaldelta" repos

  1   2   3   >