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
[email protected]
https://mail.p
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
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
>
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.
>
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
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
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
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
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:
> &
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
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
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
suggesting, but on a local level.
In my "testing" branch, I have added support for this in "make check".
>
> -Brett
> ___
> python-committers mailing list
> [email protected]
> http://mail.python.org/mail
-- Forwarded message --
From: Benjamin Peterson <[EMAIL PROTECTED]>
Date: Thu, Aug 21, 2008 at 1:58 PM
Subject: Re: [python-committers] Trunk and 3.0 branch are now open
To: Brett Cannon <[EMAIL PROTECTED]>
On Thu, Aug 21, 2008 at 1:30 PM, Brett Cannon <[EMAIL PR
by going to Search and choosing "needs
> review" under the Keyword pull-down.
Or you can click "edit" by "Your queries" and select the "Needs review" query.
--
Cheers,
Benjamin Peterson
"There's no place like 127.0.0.1."
__
; they are not
> mutually exclusive.
To help out your reviewers, you also might want to put your patch on
Rietveld. I personally prefer using it instead of finding the files I
need to compare the patch to manually and calculating out lines
numbers etc.
>
> -Brett
>
--
Cheers,
Ben
und and doesn't involve the heavy lifting of 2to3; even if you
aren't very familiar with 2to3, you could review it.)
>
> Regards
>
> Antoine.
>
>
> ___
> python-committers mailing list
> python-committers@python
o make any changes.
>
> Why freeze the 3.0 branch?
So he can release 3.0rc2, I imagine.
--
Cheers,
Benjamin Peterson
"There's no place like 127.0.0.1."
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
ild-installer.py?)
I had to hack the thing up a bit to get it to work. It's ugly, though,
so I'll have to clean it up and commit sometime.
--
Cheers,
Benjamin Peterson
"There's nothing quite as beautiful as an oboe... except a chicken
stuck in a vacuum cleaner."
On Thu, Oct 2, 2008 at 6:28 PM, Jeff Senn <[EMAIL PROTECTED]> wrote:
>
> On Oct 2, 2008, at 6:26 PM, Benjamin Peterson wrote:
>
>> On Thu, Oct 2, 2008 at 4:51 PM, Jeff Senn <[EMAIL PROTECTED]> wrote:
>>>
>>> Is whoever does the OS-X build on this list?
still am quite
inexperienced and gladly step aside for anyone who's been around
longer.
--
Cheers,
Benjamin Peterson
"There's nothing quite as beautiful as an oboe... except a chicken
stuck in a vacuum cleaner."
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
olved. And looking at the
tracker, I only see 18 release blockers.
--
Cheers,
Benjamin Peterson
"There's nothing quite as beautiful as an oboe... except a chicken
stuck in a vacuum cleaner."
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/python-committers
>
--
Cheers,
Benjamin Peterson
"There's nothing quite as beautiful as an oboe... except a chicken
stuck in a vacuum cleaner."
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
On Fri, Oct 17, 2008 at 1:26 PM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On Oct 3, 2008, at 4:55 PM, Benjamin Peterson wrote:
>
>> On Fri, Oct 3, 2008 at 7:09 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
&g
On Thu, Nov 6, 2008 at 9:53 PM, Steve Holden <[EMAIL PROTECTED]> wrote:
>
> Which reminds me, now 3.0 is final does this mean the Grand Library
> Reorganization has to wait until 4.0?
PEP 3118 has been implemented.
--
Cheers,
Benjamin Peterson
"There's nothing quit
t; Mac/BuildScript/...
> ___
> python-committers mailing list
> [email protected]
> http://mail.python.org/mailman/listinfo/python-committers
>
--
Cheers,
Benjamin Peterson
"There's nothing quite as beautiful as
On Sun, Jan 4, 2009 at 5:22 PM, Georg Brandl wrote:
> Quick note:
>
> I've extended the pre-commit hook to also check documentation files (*.rst)
> for trailing whitespace and tabs.
Does "make patchcheck" also run the whitespace checker?
--
Regards,
Benjamin
___
On Sun, Jan 25, 2009 at 11:12 AM, Guido van Rossum wrote:
> 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?
He also has annoying habit of "reopening" issues by duplicating
another one
On Wed, Feb 25, 2009 at 6:14 PM, Mark Hammond wrote:
>
> To the best of my knowledge, bzr's support for this is a few months away. I
> keep hearing rumours mercurial does support it and I'm just starting work on
> a mercurial based project, so I may be able to find some answers there -
> does any
2009/3/1 Nick Coghlan :
> Martin v. Löwis wrote:
>> and that it takes forever
>
> Not sure about that - I *do* port my own changes, and while the merges
> are quicker than a full recompile or running the test suite, they're
> still far, far, slower than applying an equivalent patch or doing an svn
Please no checkins in branches/py3k until I give the word. Thanks.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
branches/py3k is now open for work on the second 3.1 alpha.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
I'm going to release 3.1a2 now. Please don't commit anything without
my blessing. I'm on #python-dev on Freenode, and you can always email
me.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/ma
Happy hacking on beta 1!
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
2009/4/5 Matthias Klose :
> While looking at the diffs between the 261 release tags and the 26 branch, I
> noticed many items in Misc/NEWS appearing in the 2.6.1 or even 2.6 sections.
> I moved all of these to 2.6.2, after checking some of them, and found all of
> the
> checked ones be backported
While I'm making 3.1 beta 1, the py3k branch is hereby frozen.
--
Thanks,
Benjamin
(Here's some extra characters, so the spam filter doesn't catch this.
blah, balh, balh)
___
python-committers mailing list
[email protected]
http://mail.pytho
I've released the beta, so the branch is now open.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
I've released 3.1 beta 1, so the branch is now open.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
I'm going to do the release candidate now.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
branches/py3k is now open for bug fixes.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Please no commits until I'm done with this release. Thanks!
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Remember: Be extremely conservative with commits now!
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
The py3k branch is now frozen for 3.1 final to be tagged. If you need
to contact me, I will be watching my inbox and on Freenode IRC
#python-dev. The tree will be frozen for about a day, so binaries can
be built.
--
Regards,
Benjamin
___
python-committe
Now that 3.1 is released, branches/py3k is open for 3.2, and
branches/release31-maint is open for 3.1.1.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
If you have features that were added while 3.1 was in feature freeze,
please merge them.
Thanks,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
2009/7/2 Jesus Cea :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> I have found a few flaws in 2.6 documentation. I was going to correct
> them when I found they are already solved in trunk in r69846, done by
> mark.dickinson in february.
>
> Is there any reason for that commit not to be me
2009/7/2 Jeroen Ruigrok van der Werven :
> -On [20090702 17:15], Jesus Cea ([email protected]) wrote:
>>Ughhh. This is actually a good reason to migrate to mercurial, were
>>merges are painless :-).
>
> For all I know Mercurial doesn't make the issue of resolving content merges
> easier, so that would m
2009/7/2 Christian Heimes :
> Barry Warsaw wrote:
>> I will announce this to py-list, py-ann, and update the 3.0 download pages.
>>
>> There will be no 3.0.2.
>
> +1 for your decision.
>
> Are there any known incompatibilities that could break a Python 3.0
> script on 3.1?
This is the short list:
2009/7/7 Georg Brandl :
> I think this should be reverted -- the support code is not for the
> bsddb module, but for building the dbm module with bsddb.
Would you mind doing the honors? I'm on holiday.:)
--
Regards,
Benjamin
___
python-committers mai
Since we are living in 2009 now, I've changed the encodings of
Misc/ACKS and Misc/NEWS to UTF-8 from latin-1.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Hi everyone,
I'm just getting back from the nice trip to the Olympic Peninsula. I
should be able to do a release sometime next week. In the meantime,
could someone post the patch to the 3.1 download site? (We should add
a note to the quick links section, too.)
2009/8/6 Georg Brandl :
> We can eith
I'm going to start working on 3.1.1 now. Please no commits to it.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
2009/8/13 Brett Cannon :
> Is this an alpha or beta cut for 3.1.1? I have a crasher fix I plan to
> commit later today.
I'm calling it an RC. Feel free to commit that fix now that I've
tagged the release.
--
Regards,
Benjamin
___
python-committers ma
3.1.1 is out, so the maintence branch is open for 3.1.2.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
2009/9/13 Brett Cannon :
> issue6844 wants to stop a warning from being raised when someone
> accesses a 'message' attribute on an exception when it is set by the
> user (currently any usage of the 'message' attribute raises a
> warning). To do this properly is going to require some state flag on
>
2009/9/18 Jesse Noller :
> 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/PyM
I'm going to cut the 2.7a1 release now, so please no checkins until I
give the all clear. Thank you!
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
The alpha is out, so feel free to commit again.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Please no commits in the trunk until I finish with 2.7a2. Thanks!
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
With 2.7a2 out, the trunk is now available for development towards 2.7 alpha 3.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Please no checkins to the trunk while I do the release.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
2.7a3 is out, so feel free to commit again.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
2010/2/20 Jeffrey Yasskin :
> Hi all,
>
> David Malcolm is the Fedora maintainer for the Python package and has
> written a gdb plugin to replace and dramatically improve our old
> Misc/gdbinit file using the new python scripting support in gdb-7. You
> can see it in action at
> http://fedoraprojec
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 that is done any more.
>
> Georg and Benjamin used to d
I'm going to start working on these two releases, so please refrain
from making checkins in the trunk or the 3.1 branch. Thanks!
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo
With 3.1.2rc2 and 2.7a4 out, the trunk and the 3.1 branch are open to commits.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
2010/3/13 Jesus Cea :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/13/2010 11:25 PM, Barry Warsaw wrote:
>> On Mar 13, 2010, at 08:42 PM, Jesus Cea wrote:
>>
>>> I was wondering about http://bugs.python.org/issue3928 . It is a trivial
>>> fix a couple of lines long only.
>>
>> These
2010/3/13 "Martin v. Löwis" :
What about 3.1.3, Benjamin?. I guess it is too late for 3.1.2,
since the rc is out. I saw your message asking for stopping commits
the 6th march, but I haven't seen another message opening the gates
again...
>>> As Martin pointed out, I don't think
2010/3/13 Jesus Cea :
> I will commit the patch to trunk and py3k, and to 2.6 and 3.1 branch
> after 2.6.5 and 3.1.2 are out.
>
> Should I commit now to trunk/py3k and later to 2.6/3.1, or wait to do
> the four commits at the same time?. Don't want to miss the 2.7beta.
That's up to you.
>
> Mercu
2010/3/17 Nick Coghlan :
> Short version: SVN and other non-DVCS systems don't store enough (or the
> right) metadata to support merging properly, so branching becomes
> unnecessarily painful.
This isn't really true these days given svn merge --reintegrate.
--
Regards,
Benjamin
___
There are now no 3.1 release blockers, so on with the release!
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
The 3.1 branch is now open for the first palindrome release in 3.x. :)
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Let's do it. Please no commits to the trunk which are not aimed at
fixing the current buildbot failures. Thank you!
2010/4/6 "Martin v. Löwis" :
> Benjamin Peterson wrote:
>> I propose that we freeze the trunk except for fixes for the buildbots.
>> Thoughts?
&g
2010/4/6 "Martin v. Löwis" :
>> 1. Ships 2.7.0 with current pybsddb code. The CObject deprecation is
>> currently silenced explictly.
>
> This is what I recommend to do. CObject should not be deprecated for
> 2.x, so bsddb using it is just fine - no need for change.
I think this option is best, t
Time to release the first beta.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Commit away! I look forward to seeing more green buildbots for the next beta.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
I'm going to release 2.7 beta 2 now, so the trunk is frozen until that's done.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
With 2.7b2 done, the trunk is open for commits. Keep in mind that the
next release will be a release candidate.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committer
I'm now releasing 2.7rc1, so please no commits.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
Python 2.7 release candidate 1 has been released. That means the trunk
is open, but we are also now in the final development phase for Python
2.7. Stability is the top priority now. Please be very careful about
what you change now, ensuring that your alterations will not have
unexpected consequence
I apologize for silently missing 2.7rc2 today; an event ran longer
than I anticipated. I plan to release tomorrow, Sunday.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/pytho
So please no trunk commits!
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
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
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
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
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
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
[email protected]
http://mail.python.org/mailman
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
[email protected]
http://mail.python.org/mailm
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
_
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
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
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
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
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
>>> :-)
All branches are closed now. I'll be on #python-dev and on email if you need me.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
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
[email protected]
http://mail.python.org/mailman/listinfo/pyt
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
I'm going to start working on the releases now, so the maintenance
branches are now closed.
--
Regards,
Benjamin
___
python-committers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/python-committers
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
[email protected]
http://mail.python.org/mailman/l
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
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
1 - 100 of 170 matches
Mail list logo
