-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/18/2011 10:46 PM, anatoly techtonik wrote:
> On Wed, May 18, 2011 at 10:37 PM, Georg Brandl wrote:
>> On 18.05.2011 21:09, "Martin v. Löwis" wrote:
>>> Am 18.05.2011 20:39, schrieb Hagen Fürstenau:
> On behalf of the Python development team,
> 3.2.1b1 was already merged back. (And 3.2.1rc1 will also be merged back
> soon, since there will be a 3.2.1rc2.)
Thanks for the clarification! :-)
Cheers,
Hagen
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinf
On 18.05.2011 21:37, Hagen Fürstenau wrote:
>> P.S. "Shouldn't" makes it sound as if there was a mistake.
>
> Well, I thought there was. When do these tags get merged into "cpython"
> then? "v3.2.1b1" is there, but "v3.2.1rc1" isn't:
>
> http://hg.python.org/cpython/tags
3.2.1b1 was already merg
> Can't this work be done in the branch of main repo, so that everybody
> can track the progress in place? Is there any picture of the process
> similar to http://nvie.com/posts/a-successful-git-branching-model/ ?
It *is* a branch of the main repo, so everybody *can* track the progress
(not sure w
On 5/18/2011 10:46 PM, anatoly techtonik wrote:
On Wed, May 18, 2011 at 10:37 PM, Georg Brandl wrote:
On 18.05.2011 21:09, "Martin v. Löwis" wrote:
http://hg.python.org/releasing/3.2.1/
To clarify: once the final is done, the repo Martin mentioned will be
merged back to main and then vani
On Wed, May 18, 2011 at 10:37 PM, Georg Brandl wrote:
> On 18.05.2011 21:09, "Martin v. Löwis" wrote:
>> Am 18.05.2011 20:39, schrieb Hagen Fürstenau:
On behalf of the Python development team, I am pleased to announce the
first release candidate of Python 3.2.1.
>>>
>>> Shouldn't there b
Am 18.05.2011 21:37, schrieb Hagen Fürstenau:
>> P.S. "Shouldn't" makes it sound as if there was a mistake.
>
> Well, I thought there was. When do these tags get merged into "cpython"
> then?
See PEP 101
Regards,
Martin
___
Python-Dev mailing list
Pyt
On 18.05.2011 21:09, "Martin v. Löwis" wrote:
> Am 18.05.2011 20:39, schrieb Hagen Fürstenau:
>>> On behalf of the Python development team, I am pleased to announce the
>>> first release candidate of Python 3.2.1.
>>
>> Shouldn't there be a tag "v3.2.1rc1" in the hg repo?
>
> http://hg.python.org
> P.S. "Shouldn't" makes it sound as if there was a mistake.
Well, I thought there was. When do these tags get merged into "cpython"
then? "v3.2.1b1" is there, but "v3.2.1rc1" isn't:
http://hg.python.org/cpython/tags
Cheers,
Hagen
___
Python-Dev maili
Am 18.05.2011 20:39, schrieb Hagen Fürstenau:
>> On behalf of the Python development team, I am pleased to announce the
>> first release candidate of Python 3.2.1.
>
> Shouldn't there be a tag "v3.2.1rc1" in the hg repo?
http://hg.python.org/releasing/3.2.1/
Regards,
Martin
P.S. "Shouldn't" mak
> On behalf of the Python development team, I am pleased to announce the
> first release candidate of Python 3.2.1.
Shouldn't there be a tag "v3.2.1rc1" in the hg repo?
Cheers,
Hagen
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
On Wed, May 18, 2011 at 9:26 PM, Victor Stinner
wrote:
>
> Oh, I like it. But the output should be reST to be able to include it
> directly in the Python documentation. Sphinx would generate a new table
> of contents with links to each release.
As Georg noted, Misc/NEWS is already ReST. My propos
On 18.05.2011 14:06, Victor Stinner wrote:
> Le mercredi 18 mai 2011 à 13:35 +0200, Georg Brandl a écrit :
>> On 18.05.2011 13:26, Victor Stinner wrote:
>>
>> >> See
>> >>
>> >> http://dev.pocoo.org/~gbrandl/news.html
>> >>
>> >> which I made as an experiment a while ago.
>> >
>> > Oh, I like i
Le mercredi 18 mai 2011 à 13:35 +0200, Georg Brandl a écrit :
> On 18.05.2011 13:26, Victor Stinner wrote:
>
> >> See
> >>
> >> http://dev.pocoo.org/~gbrandl/news.html
> >>
> >> which I made as an experiment a while ago.
> >
> > Oh, I like it. But the output should be reST to be able to include
On 18.05.2011 13:26, Victor Stinner wrote:
>> See
>>
>> http://dev.pocoo.org/~gbrandl/news.html
>>
>> which I made as an experiment a while ago.
>
> Oh, I like it. But the output should be reST to be able to include it
> directly in the Python documentation. Sphinx would generate a new table
>
On Wed, May 18, 2011 at 01:26:40PM +0200, Victor Stinner wrote:
> > http://dev.pocoo.org/~gbrandl/news.html
> >
> Oh, I like it. But the output should be reST to be able to include it
> directly in the Python documentation. Sphinx would generate a new table
Interesting ideas! It would be really u
Le mercredi 18 mai 2011 à 12:58 +0200, Georg Brandl a écrit :
> On 18.05.2011 12:49, Nick Coghlan wrote:
> > On Wed, May 18, 2011 at 5:57 PM, Georg Brandl wrote:
> >> On 18.05.2011 08:34, "Martin v. Löwis" wrote:
> > That's great, but where is the list if changes?
>
> All changes are
On Wed, May 18, 2011 at 8:50 PM, anatoly techtonik wrote:
> I believe you misunderstood. If you follow what's new link above, you
> will see a link to Misc/NEWS, but this one leads to
> http://hg.python.org/cpython/file/default/Misc/NEWS where no
> references to 3.2.1 are available.
Ah, I see wha
On 18.05.2011 12:50, anatoly techtonik wrote:
> On Wed, May 18, 2011 at 1:40 PM, Nick Coghlan wrote:
>> On Wed, May 18, 2011 at 5:58 PM, anatoly techtonik
>> wrote:
>>> On Wed, May 18, 2011 at 9:18 AM, Amaury Forgeot d'Arc
>>> wrote:
Hi,
2011/5/18 anatoly techtonik :
> That's
On Wed, May 18, 2011 at 8:58 PM, Georg Brandl wrote:
> On 18.05.2011 12:49, Nick Coghlan wrote:
>> Wishlist item: How hard would it be to run a ReST parser over
>> Misc/NEWS and create a HTML version for inclusion in the release
>> pages? (Bonus points if it steals the issue reference linkificatio
On 18.05.2011 12:49, Nick Coghlan wrote:
> On Wed, May 18, 2011 at 5:57 PM, Georg Brandl wrote:
>> On 18.05.2011 08:34, "Martin v. Löwis" wrote:
> That's great, but where is the list if changes?
All changes are always listed in the Misc/NEWS file.
A "Change log" link on every do
On Wed, May 18, 2011 at 1:40 PM, Nick Coghlan wrote:
> On Wed, May 18, 2011 at 5:58 PM, anatoly techtonik
> wrote:
>> On Wed, May 18, 2011 at 9:18 AM, Amaury Forgeot d'Arc
>> wrote:
>>> Hi,
>>>
>>> 2011/5/18 anatoly techtonik :
That's great, but where is the list if changes?
>>>
>>> All ch
On Wed, May 18, 2011 at 5:57 PM, Georg Brandl wrote:
> On 18.05.2011 08:34, "Martin v. Löwis" wrote:
That's great, but where is the list if changes?
>>>
>>> All changes are always listed in the Misc/NEWS file.
>>> A "Change log" link on every download page displays this file.
>>
>> I think it
On Wed, May 18, 2011 at 5:58 PM, anatoly techtonik wrote:
> On Wed, May 18, 2011 at 9:18 AM, Amaury Forgeot d'Arc
> wrote:
>> Hi,
>>
>> 2011/5/18 anatoly techtonik :
>>> That's great, but where is the list if changes?
>>
>> All changes are always listed in the Misc/NEWS file.
>> A "Change log" li
On Wed, May 18, 2011 at 9:34 AM, "Martin v. Löwis" wrote:
>>> That's great, but where is the list if changes?
>>
>> All changes are always listed in the Misc/NEWS file.
>> A "Change log" link on every download page displays this file.
>
> I think it would be good if the release announcement made s
On Wed, May 18, 2011 at 9:18 AM, Amaury Forgeot d'Arc
wrote:
> Hi,
>
> 2011/5/18 anatoly techtonik :
>> That's great, but where is the list if changes?
>
> All changes are always listed in the Misc/NEWS file.
> A "Change log" link on every download page displays this file.
I actually followed htt
On 18.05.2011 08:34, "Martin v. Löwis" wrote:
>>> That's great, but where is the list if changes?
>>
>> All changes are always listed in the Misc/NEWS file.
>> A "Change log" link on every download page displays this file.
>
> I think it would be good if the release announcement made some
> summa
>> That's great, but where is the list if changes?
>
> All changes are always listed in the Misc/NEWS file.
> A "Change log" link on every download page displays this file.
I think it would be good if the release announcement made some
summary statement, though, like "NNN bugs have been fixed, in
Hi,
2011/5/18 anatoly techtonik :
> That's great, but where is the list if changes?
All changes are always listed in the Misc/NEWS file.
A "Change log" link on every download page displays this file.
--
Amaury Forgeot d'Arc
___
Python-Dev mailing list
That's great, but where is the list if changes?
--
anatoly t.
On Tue, May 17, 2011 at 9:50 PM, Georg Brandl wrote:
> On behalf of the Python development team, I am pleased to announce the
> first release candidate of Python 3.2.1.
>
> Python 3.2.1 will the first bugfix release for Python 3.2, f
On behalf of the Python development team, I am pleased to announce the
first release candidate of Python 3.2.1.
Python 3.2.1 will the first bugfix release for Python 3.2, fixing over 120
bugs and regressions in Python 3.2.
For an extensive list of changes and features in the 3.2 line, see
ht
31 matches
Mail list logo
