I'll volunteer to do a French translation of the release.
--
Cheers,
Hasan Diwan <[EMAIL PROTECTED]>
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options
Barry Warsaw schrieb:
> PEP 101 is sorely out of date, especially with regards to updating web
> content and the Python documentation. I think I now know how to
> update the python.org web site, but the new Python documentation
> format is still a mystery to me. If someone would like to help upd
On 3/1/08, Christian Heimes <[EMAIL PROTECTED]> wrote:
> When 3.0a2 was released I contacted two larger German IT news sites. Non
> of them even bother to reply. :/
>
> I propose that we provide two official texts for the press. A shorter
> text which explains Python and the most important chan
Barry Warsaw wrote:
> On behalf of the Python development team and the Python community, I'm
> happy to announce the first alpha release of Python 2.6, and the third
> alpha release of Python 3.0.
Cool! :)
But how comes the release notes for Python 3a3 on the download site are the
same as for 3a2
Christian Heimes wrote:
> Stefan Behnel wrote:
>> I would like to know how stable the C-API of Python 3 is, or what the
>> expected
>> release level (beta?) would be at which I can expect it to stabilise. What is
>> the plan here?
The release schedule in PEP 3000 says "August 2008" for 3.0 final,
Christian Heimes writes:
> It may sound like a dumb question by why do we need a release tool
> at all? I was involved in the release process of 3.0a2. Almost
> every step of the build process required human interaction.
Interaction, yes, but often it can be reduced to "Abort, retry, fail?"
On Sat, Mar 1, 2008 at 12:14 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
...
> The 3.0 API isn't stable yet. I plan to rename some of the functions
> before the first beta is released. Currently the naming schema is too
> confusing:
>
> PyUnicode - str
> PyString - bytes
> PyBytes - by
On Sat, Mar 1, 2008 at 11:11 AM, Barry Warsaw <[EMAIL PROTECTED]> wrote:
...
> > I also propose translations of the shorter text to important languages
> > like French, German, Japanese, Portuguese and Spanish. I'm willing to
> > help with the German translation.
>
> Cool, thanks.
I'd like
Barry> The dependency on gtk is unnecessary and means it can effectively
Barry> only be run on Linux. Specifically it means I can't do releases
Barry> on OS X. I don't see much benefit in having a gui tool for doing
Barry> releases.
Gtk and Glade are available through MacPorts,
> It may sound like a dumb question by why do we need a release tool at
> all? I was involved in the release process of 3.0a2. Almost every step
> of the build process required human interaction. I don't want to
> diminish the effort that was put into welease though. But maybe (!) the
> same time
Martin v. Löwis wrote:
> I guess every release manager is free to come up with his own set of
> tools, but I feel you've given up too quickly (or started too late -
> perhaps a test release run a few days before the release would have
> helped).
>
> In any case, I'm willing to help with welease, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 5:37 PM, Martin v. Löwis wrote:
>> With apologies to Anthony, welease is crack. I made pretty good
>> progress once I ditched it and starting doing things manually.
>> Between now and the next alpha I intend to work on a com
> The 2.6a1 x86 MSI is there, but the 3.0a3 x86 MSI is still giving a 404.
Please try again - *those* files weren't actually there when I sent my
last message; I just built them.
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://m
> Thanks for fixing these Martin!
I have now also uploaded signed MSI files for 3.0a3.
I have not tested them on a machine which doesn't have the
VS 2008 CRT installed (as all the machines I can access
right now do have it); please report what works and what
doesn't.
Regards,
Martin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 3:04 PM, Christian Heimes wrote:
> I *never* sync changes from trunk Misc/NEWS to py3k Misc/NEWS. From my
> point of view it doesn't make sense to put Python 2.6 changes in the
> same section as Python 3.0 changes. Moving changes fr
On 01/03/2008, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > As of 4:50 PM EST, the links to Windows installers give 404 File Not
> > Found.
> >
> > I gather that they are still in process,
> > and notice that there is no public c.l.p. announcement.
>
>
> I just fixed that. The files were t
> With apologies to Anthony, welease is crack. I made pretty good
> progress once I ditched it and starting doing things manually.
> Between now and the next alpha I intend to work on a command line
> script to help with releases. If you're interested in helping, let me
> know.
I guess
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 5:26 PM, Martin v. Löwis wrote:
>> As of 4:50 PM EST, the links to Windows installers give 404 File Not
>> Found.
>>
>> I gather that they are still in process,
>> and notice that there is no public c.l.p. announcement.
>
> I just
> As of 4:50 PM EST, the links to Windows installers give 404 File Not
> Found.
>
> I gather that they are still in process,
> and notice that there is no public c.l.p. announcement.
I just fixed that. The files were there; just the links were wrong.
Regards,
Martin
__
Stefan Behnel wrote:
> I would like to know how stable the C-API of Python 3 is, or what the expected
> release level (beta?) would be at which I can expect it to stabilise. What is
> the plan here?
>
> The background is Cython, which will need to support Python 3 one day or
> another, so I wanted
Barry Warsaw wrote:
> I will definitely need help keeping the various NEWS files up to
> date. I don't see any way that I'll be able to spend time on these
> when I'm cutting a release. Python 2.6 NEWS was simply impossible to
> proofread because of its sheer size and the fact that it was the fir
Hi all,
I would like to know how stable the C-API of Python 3 is, or what the expected
release level (beta?) would be at which I can expect it to stabilise. What is
the plan here?
The background is Cython, which will need to support Python 3 one day or
another, so I wanted to know from which poin
Steve Holden wrote:
> PyCon is using a PR team to help with publicity. Maybe we can ask them
> for assistance on how to get the word out?
That's a *very* good idea! Let's ask some professionals rather than
writing something on our own.
Christian
___
Py
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 1:56 PM, Christian Heimes wrote:
> Barry Warsaw wrote:
>> In this case, there was a lot more work to do because 2.6 wasn't tied
>> in at all. Add to the fact that I didn't have any experience with
>> the
>> website infrastructure
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just announced the 2.6a1 and 3.0a3 releases, and am thawing both
branches.
Just some quick feedback in case anybody is interested. First, huge
thanks go to Brett Cannon, Neal Norwitz, Mark Dickinson and Fred Drake
for their help last night. A
Barry Warsaw wrote:
> In this case, there was a lot more work to do because 2.6 wasn't tied
> in at all. Add to the fact that I didn't have any experience with the
> website infrastructure made things a bit more difficult the first time
> out. I still don't quite have the 2.6 links working correc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team and the Python community, I'm
happy to announce the first alpha release of Python 2.6, and the third
alpha release of Python 3.0.
Python 2.6 is not only the next advancement in the Python 2 series, it
is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 10:38 AM, Steve Holden wrote:
> Barry Warsaw wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On Mar 1, 2008, at 12:36 AM, Steve Holden wrote:
>>
>>> If you can document the web stuff you have to do I will formalize
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mar 1, 2008, at 12:36 AM, Steve Holden wrote:
> If you can document the web stuff you have to do I will formalize it
> as
> a procedure for use in future releases.
Hi Steve,
In this case, there was a lot more work to do because 2.6 wasn't tied
29 matches
Mail list logo
