Brett Cannon schrieb:
Another person requesting their privs be removed.
I've now removed all four keys in question from the repository.
Georg
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pyth
Richard Jones schrieb:
> On Mon, 4 Aug 2008, Brett Cannon wrote:
>> Another person requesting their privs be removed.
>
> There's no sense in me having commit privs these days either. Haven't used
> them since NFS! Please revoke.
Done.
Georg
___
pyth
Christian Heimes schrieb:
> 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
Barry Warsaw schrieb:
> => python-committers
>
> On Dec 5, 2008, at 3:21 AM, Georg Brandl wrote:
>
>>> In the meantime, I'll make sure Georg is involved in point releases
>>> moving forward.
>
>> That's good. Thanks!
>
> I t
Quick note:
I've extended the pre-commit hook to also check documentation files (*.rst)
for trailing whitespace and tabs.
If you find a bug that doesn't let you commit legitimate content, please
notify me.
Thanks,
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no le
Christian Heimes schrieb:
> 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
> reacte
Matthias Klose schrieb:
> Guido van Rossum schrieb:
>> I'm not sure I understand your request. Is it okay to build docs using
>> a version of sphinx that is included in the distro? Is there a
>> specific revision that you would like to see rolled back, or do you
>> have a specific fix in mind?
>
>
Trent Nelson schrieb:
> And last but not least, thanks to Guido and all the Python committers
> for their tireless efforts to date. Although the sheer elegance of
> the language is what initially attracted me to Python, it was the
> developer community that made me want to stick
M.-A. Lemburg schrieb:
> IMHO, those are all feel-good factors which can easily be had by
> installing a local Subversion repo copy (sync'ed using svnsync (*)),
> except perhaps regarding merging - but I don't know anything about
> in what way the DVCSes are better than Subversion.
>
> (*) This p
Martin v. Löwis schrieb:
>> Could you clarify for me: how binding will your PEP be? ie, will it
>> be closer to a recommendation, or will the final PEP be a final
>> decision about what will (or will not) happen?
>
> If the PEP process is followed (which I recommend it is), then it will
> be a d
Antoine Pitrou schrieb:
> Le jeudi 26 février 2009 à 17:10 +0100, M.-A. Lemburg a écrit :
>> This is probably a matter of Internet connection bandwidth then.
>
> Not really.
> To give a point of comparison, when I clone (using Mercurial) the Python
> trunk at http://code.python.org/hg/trunk, it ta
Amaury Forgeot d'Arc schrieb:
> On Tue, Apr 7, 2009 at 06:06, Hirokazu Yamamoto
> wrote:
>>
>> Barry Warsaw wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On Apr 6, 2009, at 9:58 PM, Barry Warsaw wrote:
>>>
The release is tagged. Martin, can you build the Windows in
I just wanted to merge a series of commits to py3k where the first
added a new file, and the others changed it. Output was:
property 'svnmerge-integrated' deleted from '.'.
property 'svnmerge-blocked' deleted from '.'.
--- Merging r71409 into '.':
ADoc/tools/sphinxext/static/basic.css
sv
Georg Brandl schrieb:
> I just wanted to merge a series of commits to py3k where the first
> added a new file, and the others changed it. Output was:
>
> property 'svnmerge-integrated' deleted from '.'.
>
>
>
> property 'svnmerge-blocke
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 videos at a PyCon (both?)
Christian Heimes schrieb:
> 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 par
I think this should be reverted -- the support code is not for the
bsddb module, but for building the dbm module with bsddb.
Georg
benjamin.peterson schrieb:
> Author: benjamin.peterson
> Date: Fri Jul 3 15:22:00 2009
> New Revision: 73807
>
> Log:
> rip out bsddb support code
>
> Modified:
>
Antoine Pitrou schrieb:
> Hello,
>
> A data corruption issue has been discovered in the C IO lib in Python
> 3.1 (http://bugs.python.org/issue6629). I've applied a fix, and I wonder
> whether we should make a release quickly to minimize the probability of
> users hitting the problem?
> (Georg tell
ould add
> a note to the quick links section, too.)
>
> 2009/8/6 Georg Brandl :
>> We can either make a release with only that patch applied, or a release of
>> the full 3.1-maint branch, but the latter would need alphas and betas.
>
> Why does that require doing alphas
Antoine Pitrou schrieb:
> Le jeudi 06 août 2009 à 23:32 -0700, Raymond Hettinger a écrit :
>> > I just meant to +1 the "we need to make a new micro-release right now"
>> > paragraph. Logistically, I think it needs to be a full binary release
>> > but it could be identical to 3.1 except for the one
Brett Cannon schrieb:
>> brainstorm:
>>
>> It'd be nicer if we could generate the file from another source,
>> perhaps keep each releases news in its own file and merge it all
>> together at release time?
>>
>> Or have a NEWS.latest file that contains only updates since the
>> previous release (pa
entry ends up being rewritten from the commit message to
> be more user-focussed description of the change...
>
>> On Sep 14, 2009 6:33 PM, "Georg Brandl" > <mailto:[email protected]>> wrote:
>>
>> Brett Cannon schrieb:
>>
>> >> brainst
R. David Murray schrieb:
> On Mon, 14 Sep 2009 at 12:40, Georg Brandl wrote:
>> Yes, but still: in many cases they are very similar.
>>
>> Plus, it's hard to auto-add a NEWS entry from a commit message (because
>> you need to determine the right section), while it&
Jesse Noller schrieb:
> I would like to propose we give the commit bit to Doug Hellmann in
> order for him to help out with documentation and GHOP style tasks
> (he's helped in the past).
>
> You might know him from the "Python Module of the Week" series here:
>
> http://www.doughellmann.com/PyMO
Am 01.03.2010 09:44, schrieb Steven Bethard:
> I'm preparing the argparse module for the 2.7 and 3.2 branches. Could
> someone remind me again what the commit process is? Commit to 2.7 and
> merge to 3.2? And do we merge with svnmerge.py or svn merge? There's
> probably a webpage explaining this so
Am 01.03.2010 23:44, schrieb Benjamin Peterson:
> 2010/3/1 Brett Cannon :
>>
>>
>> On Mon, Mar 1, 2010 at 09:31, Eric Smith wrote:
>>> I've been doing it to remind myself of things that need to be merged, or
>>> not. And I believe it used to be used by people doing mass-merges, I'm not
>>> sure if
Am 13.03.2010 17:51, schrieb Barry Warsaw:
> I'm not necessarily saying these shouldn't go into 2.6.5, but this late in
> the release cycle, every change needs to be justified. My preferred way of
> doing so is by filing a release blocker issue stating and backing up the
> requested change. We ca
Am 14.03.2010 00:08, schrieb Barry Warsaw:
> On Mar 13, 2010, at 07:11 PM, Georg Brandl wrote:
>
>>No need to file a new issue -- I've promoted 8111 to release blocker.
>>I've added an explanation and a collective diff. No further RC is needed.
>
> Thanks;
Am 14.03.2010 00:35, schrieb Georg Brandl:
> Am 14.03.2010 00:08, schrieb Barry Warsaw:
>> On Mar 13, 2010, at 07:11 PM, Georg Brandl wrote:
>>
>>>No need to file a new issue -- I've promoted 8111 to release blocker.
>>>I've added an explanation and
Am 14.03.2010 00:53, schrieb "Martin v. Löwis":
>> Thinking of that a bit more: after the Hg transition, shouldn't we be able to
>> really freeze a branch that is in pre-release approval-needed mode? It is
>> trivial for anyone to commit a fix to their own branch, and then instead of
>> pushing th
Am 20.03.2010 00:03, schrieb Barry Warsaw:
> Thank you everybody for a great release. The release26-maint branch is now
> open for business. "Eep eep".
I didn't hear anything about docs?
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the numb
Hi,
to make my life easier, I'd like to block all unmerged commits in 2.6 that
nobody will merge anyway. I use ``svnmerge avail --log`` to find out which
commits I have to merge, and with the current number of unmerged commits it
is taking longer and longer.
Does anyone else use svnmerge integra
Hi,
I'm delaying the 3.2 alpha1 release by one week; I don't have enough time
to sort through all the possible issues and get acquainted with the release
machinery this weekend.
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of space
Am 29.06.2010 05:32, schrieb Senthil Kumaran:
> On Tue, Jun 29, 2010 at 3:28 AM, "Martin v. Löwis" wrote:
>>
>> The ones I want to get done are PEPs 382 and 384.
>
> Just to have the direct information on these PEPs inline.
>
> PEP 382 - Namespace Packages
> http://www.python.org/dev/peps/pep-03
Am 30.06.2010 16:43, schrieb Benjamin Peterson:
> 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
Am 02.07.2010 09:53, schrieb M.-A. Lemburg:
> M.-A. Lemburg wrote:
>> Benjamin Peterson wrote:
>>> 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 in
Hi,
since the 2.7 commits now go to release27-maint, I've added svnmerge tracking
from this branch to release26-maint. From now on, if you want to backport a
commit to 2.6 you have to select the source manually via
svnmerge merge -S /python/trunk -rREV
or
svnmerge merge -S /python/branches/rel
No commits please without my blessing. If you think you have something
that is important enough, write me an email or come to #python-dev on
freenode.
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and th
Hi,
http://bugs.python.org/issue9116 was made a blocker this morning. I can
neither verify the bug nor test the patch, so I would be grateful for any
help, especially with patch review.
Also, the Windows 3.x buildbot shows failures compiling _ssl and _hashopenssl
(for logs, see e.g. http://bit.l
Am 31.07.2010 11:23, schrieb "Martin v. Löwis":
>> Also, the Windows 3.x buildbot shows failures compiling _ssl and _hashopenssl
>> (for logs, see e.g. http://bit.ly/aSAnhh). I'd like to know if this is
>> specific to that machine (I've already mailed David about it) or a general
>> problem.
>
>
Am 31.07.2010 11:07, schrieb Georg Brandl:
> Hi,
>
> http://bugs.python.org/issue9116 was made a blocker this morning. I can
> neither verify the bug nor test the patch, so I would be grateful for any
> help, especially with patch review.
OK, since the problem the issue describ
Please commit away! (Especially, let's try to fix the tests and the
buildbots...)
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent,
Am 01.08.2010 15:49, schrieb Jesus Cea:
> How is migration to Mercurial going?. Showstoppers?.
Dirkjan is busy with his thesis for another two months. Since he's the
mastermind, nothing much will go forward unless someone else seeks
to take over his position.
I am also busy with my thesis for th
Hi,
the py3k branch is now in a "soft freeze" state for the 3.2a2 release.
Please no commits that could affect stability; doc updates and the like
are still ok.
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt inde
Am 05.09.2010 16:43, schrieb Antoine Pitrou:
>
> Hello,
>
> I propose we give commit privileges to Łukasz Langa. He has submitted
> various non-trivial patches of rather good quality (for example new
> features for ConfigParser), some of which have already been committed;
> it seems that he's mot
3.2a2 is tagged!
py3k is now completely frozen in case I mess something up.
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor
Am 05.09.2010 10:21, schrieb Georg Brandl:
> Hi,
>
> the py3k branch is now in a "soft freeze" state for the 3.2a2 release.
> Please no commits that could affect stability; doc updates and the like
> are still ok.
The branch is open again! The official announcement f
Am 05.09.2010 19:00, schrieb "Martin v. Löwis":
>> I propose we give commit privileges to Łukasz Langa. He has submitted
>> various non-trivial patches of rather good quality (for example new
>> features for ConfigParser), some of which have already been committed;
>> it seems that he's motivated t
Please coordinate your commits with me on #python-dev.
Thanks,
Georg
--
Thus spake the Lord: Thou shalt indent with four spaces. No more, no less.
Four shall be the number of spaces thou shalt indent, and the number of thy
indenting shall be four. Eight shalt thou not indent, nor either indent t
All binaries are built, commit at will. The announcement
will follow shortly.
cheers,
Georg
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
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 for
> non-commercial use. If you would like a copy of the license just email
> me and I will send it to you.
>
> As for how it is, I h
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 yea
I feel this should go here as well.
Am 26.10.2010 23:37, schrieb Georg Brandl:
> I've started a list of Demos and Tools here:
>
> https://spreadsheets.google.com/ccc?key=0AherhJVUN_I2dFNQdjNPMFdnOHVpdERSdWxqaXBkWWc&hl=en&authkey=CMWEn84C
>
> Please, feel free to co
Am 27.10.2010 19:52, schrieb Raymond Hettinger:
>
> On Oct 27, 2010, at 10:22 AM, Antoine Pitrou wrote:
>
>> I was surprised to learn that Dave Malcolm doesn't have commit
>> privileges yet. He has worked on the gdb integration and other issues. I
>> think it would be time to give him the right t
Hi,
on a request by Martin, I added another alpha to the Python 3.2 release
schedule. The scheduled releases are now
- 3.2 alpha 4: November 13, 2010
- 3.2 beta 1: December 4, 2010
- 3.2 beta 2: December 18, 2010
- 3.2 candidate 1: January 8, 2010
- 3.2 candidate 2: January 22, 2011
- 3.2 final:
Am 08.11.2010 15:30, schrieb Łukasz Langa:
> Am 08.11.2010 15:04, schrieb Benjamin Peterson:
>> I don't think you can ever automate "checking for mistakes" out of the
>> workflow. There will never be a commit hook that checks whether you
>> created a race condition or deference possibly uninitializ
... and it's release day again!
If you want to commit, please coordinate with me on #python-dev.
Thanks,
Georg
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
e found at:
http://docs.python.org/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 Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
Am 16.11.2010 19:14, schrieb Daniel Stutzbach:
> Now that I've started work at Google, I'd like to add new ssh keys so that I
> can
> commit from my work desktop and laptop. I hope that 20%-time will allow me to
> contribute to Python on a somewhat more regular basis than my previous
> sporadic
Dear fellow committers,
those of you who choose to observe commit freezes may now
again commit to trunk.
Thanks,
Georg
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Am 24.11.2010 15:53, schrieb Jesus Cea:
> On 24/11/10 14:48, Dirkjan Ochtman wrote:
>> All ssh repos can now be accessed by using ssh://[email protected]/repo
>> instead of ssh://[email protected]/repos/repo. While the old way should
>> continue to work, the new address should be considered prefe
Am 02.12.2010 04:08, schrieb R. David Murray:
> On Thu, 02 Dec 2010 02:19:25 +0100, wrote:
>> Le 01/12/2010 21:48, R. David Murray a écrit :
>> > My understanding of the current status of svnmerge block is that
>> > you should use it if it helps you and not worry about it otherwise.
>> > Georg an
Am 04.12.2010 15:01, schrieb "Martin v. Löwis":
> Am 02.12.2010 04:16, schrieb Jesus Cea:
>> On 01/12/10 22:47, R. David Murray wrote:
>>> Mercurial can't become the primary version system until after we've had
>>> a test-and-work-out-the-bugs period, so IMO that schedule is going to
>>> have to be
This is it: no more features into py3k for a few months please.
And no commits at all for now, except if you ask on #python-dev.
cheers,
Georg
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python
Am 05.12.2010 11:26, schrieb Nick Coghlan:
> On Sun, Dec 5, 2010 at 8:18 PM, Raymond Hettinger
> wrote:
>>
>> On Dec 5, 2010, at 2:14 AM, Dirkjan Ochtman wrote:
>>> Do we wait until after the 3.2 release now, or
>>> just until after the holidays?
>>
>> +1 for waiting until after the 3.2 release.
>
Hi,
I wonder if it's still necessary to provide .tar.bz2 and .tgz source
tarballs. If anything, it would be nice to provide .tar.xz in addition
to .tar.bz2, which has a nicer compression ratio:
.tgz - 13 MB
.tar.bz2 - 11 MB
.tar.xz - 8.6 MB
Georg
_
Am 05.12.2010 13:33, schrieb Jeroen Ruigrok van der Werven:
> -On [20101205 12:19], Georg Brandl ([email protected]) wrote:
>>I wonder if it's still necessary to provide .tar.bz2 and .tgz source
>>tarballs. If anything, it would be nice to provide .tar.xz in addition
>&g
Am 05.12.2010 14:58, schrieb Jeroen Ruigrok van der Werven:
> -On [20101205 13:58], Georg Brandl ([email protected]) wrote:
>>That's why I said "in addition to".
>
> My mistake, read over that.
>
>>It was just a thought I had while I watched the files u
Am 05.12.2010 16:56, schrieb Senthil Kumaran:
> On Sun, Dec 05, 2010 at 12:16:48PM +0100, Georg Brandl wrote:
>> I wonder if it's still necessary to provide .tar.bz2 and .tgz source
>> tarballs.
>
> Yes, it is necessary. People sometimes just expect it from an Open
&
Am 05.12.2010 19:16, schrieb M.-A. Lemburg:
> Georg Brandl wrote:
>> Hi,
>>
>> I wonder if it's still necessary to provide .tar.bz2 and .tgz source
>> tarballs. If anything, it would be nice to provide .tar.xz in addition
>> to .tar.bz2, which has a nicer c
Am 05.12.2010 20:39, schrieb "Martin v. Löwis":
>> I wonder if it's still necessary to provide .tar.bz2 and .tgz source
>> tarballs. If anything, it would be nice to provide .tar.xz in addition
>> to .tar.bz2, which has a nicer compression ratio:
>
> Looking at download statistics, for the 2.7 re
Hi,
after careful discussion I have come to the conclusion it is
not feasible to get the migration done in time for 3.2 final,
especially considering that December is not exactly a time
where everyone wants to be doing extra work.
All releases up and including 3.2 will therefore be made from SVN.
Am 06.12.2010 13:24, schrieb Barry Warsaw:
> On Dec 05, 2010, at 11:15 PM, Brett Cannon wrote:
>
>>It only increases complexity if we don't cut one of the tar.bz2 or tgz
>>source releases. But by offering a a tar.xz file we can give people a
>>smaller download which saves everyone time and bandwid
Please remember, no new features from this point on :)
Georg
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
g/
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.16 (GNU/Linux)
iEYEARECAAYFAkz9WcgACgkQN9GcIYhpnLBRYwCeMmH1GMmKOx9fVk8a/F0/TOzj
Vp0AoIHYBNcxV/U0AXIwMGWFHi1bAB+a
=KB
Am 07.12.2010 12:25, schrieb Jesus Cea:
> On 05/12/10 20:00, "Martin v. Löwis" wrote:
>> Personally, I'd still like to defer beta1 until after the Mercurial
>> switch (or alternatively, do the final 3.2 release from subversion
>> as Raymond suggested).
>
> I would vote +1 to deferral of beta1 unti
Hi,
it's now time for beta2; you know the drill by now: I'll be in
#python-dev on and off, if you like to commit something please
coordinate there.
Georg
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/lis
Am 20.12.2010 20:05, schrieb R. David Murray:
> Gah, I just realized that I committed something and I haven't seen
> Georg's unfreeze message yet.
>
> It was wrong anyway, so I reverted it.
Very good :)
For everyone, the branch is now open again.
Georg
_
g/
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk0Q/aAACgkQN9GcIYhpnLDf8gCgkLGAsE+T3R505jZc1RxXDYsa
NSsAnRGaFjeTm9o2Z5O8FuIzTUG8t1PT
=hH
Am 22.12.2010 02:15, schrieb Nick Coghlan:
> On Wed, Dec 22, 2010 at 6:18 AM, Georg Brandl wrote:
>> Since PEP 3003, the Moratorium on Language Changes, is in effect, there
>> are no changes in Python's syntax and built-in types in Python 3.2.
>
> Minor nit - we actua
Am 09.01.2011 00:50, schrieb Antoine Pitrou:
>
> Hello,
>
> Based on his work to diagnose and fix many issues related to OS X and/or
> IDLE/tk, I would like to propose that we give Ned Deily commit rights.
> He seems to already have developer rights on the tracker.
+1.
Georg
__
Am 09.01.2011 00:09, schrieb Terry Reedy:
> Two years ago, Eli Bendersky submitted to the tracker one of several duplicate
> reports about problems with difflib.SequenceMatcher. After I consolidated and
> closed all issues but one, he wrote me, said he wanted to get more involved in
> Python develo
Hi,
you may have noticed that 3.2rc1 was planned for today. Since there
are quite a few critical Mac issues unresolved, Ned's contacted
Ronald about them, but we haven't heard back yet. I'm going to delay
the rc for a few days to give him a bit of time (if maybe has was on
vacation this past wee
Endly, the time is right for rc1. Please coordinate in #python-dev
if you need something to go in before.
Georg
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
der trying Python 3.2 with your code and reporting any bugs
you may notice to:
http://bugs.python.org/
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.
The rc is out. Let's hope for some decent developer testing and bug reports
before it's too late...
To ensure stability in the py3k branch, I want to enforce strict discipline
for commits from now to the release. Any change needs to be reviewed by at
least one other core developer (and I mean re
Am 16.01.2011 08:53, schrieb Georg Brandl:
> The rc is out. Let's hope for some decent developer testing and bug reports
> before it's too late...
>
> To ensure stability in the py3k branch, I want to enforce strict discipline
> for commits from now to the release
Hi guys,
this is just a heads-up that I'll be freezing py3k for the rc2 release
in a bit less than 48 hours -- Sunday morning in CET.
Please get all changes that you already know are necessary reviewed and
committed *before* that: the goal is zero commits between rc2 and final
(although I know it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Both you (i.e. your earlier you) and Antoine are somewhat correct. The
mailbox module *is* broken, and such large patches *shouldn't* go in
during rc phase.
However, I don't think people are "playing games" with the release
process. No core develope
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 29.01.2011 11:16, schrieb Łukasz Langa:
> W dniu 2011-01-29 06:15, Steve Holden pisze:
>>> If the module weren't already broken for most real-world purposes I'd
>>> no question want to wait. As it is I'm on the fence.
>> Me too, but I did want to a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 29.01.2011 13:52, schrieb Antoine Pitrou:
> Le samedi 29 janvier 2011 à 12:24 +, Vinay Sajip a écrit :
>>>
>>> So my "pronouncement" here is: if reviewed properly, the patch will go
>>> in 3.2rc2. If this needs a few more days, so be it. And s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 29.01.2011 20:55, schrieb Raymond Hettinger:
> P.S. Even though it's late in the release cycle, I think we should be
> thrilled at the quality and intensity of efforts to fixup mailbox and the
> OS X issues. If these guys (Ned, Ronald, David, Ste
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, this is it: please no more commits to the py3k branch for now.
Also, for the remainder of the time until final, please make sure there
is an issue for each change you want to make containing the patch
(which was already the case for almost all c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 30.01.2011 14:49, schrieb Nick Coghlan:
> On Sun, Jan 30, 2011 at 7:52 PM, Georg Brandl wrote:
>> Changes to the "What's new" are exempt, but I would love some volunteers
>> to read through the document and note a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 30.01.2011 13:52, schrieb Nick Coghlan:
> On Sun, Jan 30, 2011 at 7:25 PM, Georg Brandl wrote:
>>> And why it does test with and without "module".
>>
>> Because it always did (there's a thing called bac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 30.01.2011 10:52, schrieb Georg Brandl:
> Okay, this is it: please no more commits to the py3k branch for now.
>
> Also, for the remainder of the time until final, please make sure there
> is an issue for each change you want to mak
der trying Python 3.2 with your code and reporting any bugs
you may notice to:
http://bugs.python.org/
Enjoy!
- --
Georg Brandl, Release Manager
georg at python.org
(on behalf of the entire python-dev team and 3.2's contributors)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.
Am 02.02.2011 17:47, schrieb Barry Warsaw:
> On Feb 02, 2011, at 01:31 PM, Michael Foord wrote:
>
>>One issue it raises is the difficulties caused by freezing the trunk for
>>releases. Instead they advocate creating the release branch at the point of
>>the release candidate instead of freezing tru
Am 02.02.2011 19:47, schrieb Antoine Pitrou:
> Le mercredi 02 février 2011 à 19:39 +0100, Jesus Cea a écrit :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 02/02/11 19:28, Antoine Pitrou wrote:
>> >> The merge here is mostly automatic. In fact, if the RM doesn't change
>> >> his/her
Am 03.02.2011 01:37, schrieb Jesus Cea:
> On 02/02/11 21:30, Barry Warsaw wrote:
>>> Just exactly the reverse of current workflow.
>
>> And for good reason (IMO). It's often much less clear exactly how far back a
>> specific patch should be committed when it's first being developed. It makes
>>
1 - 100 of 245 matches
Mail list logo
