Python 3.0 and removal of the 'string' module
bignose+hates-spam at benfinney.id.au
Sat Jul 12 02:02:19 CEST 2008
John Roth <johnroth1 at gmail.com> writes:
> On Jul 11, 6:26 am, Benjamin <musiccomposit... at gmail.com> wrote:
> > On Jul 11, 3:06 am, Ben Finney <bignose+hates-s... at benfinney.id.au>
> > wrote:
> > > Is there a better information source, then, for the current
> > > state of what's expected in Python 3.0?
> > Look at the development docs. We try to keep them up to
> > date:http://doc.python.org/dev/3.0
> The PEPs are also a good source; library changes are all listed in
> PEP 3008.
PEP 3008 doesn't seem to exist: It's not listed at the index
<URL:http://www.python.org/dev/peps/pep-0000/>, and the obvious URL
<URL:http://www.python.org/dev/peps/pep-3008/> returns a 404 response.
> PEP 361 not only gives the schedule but it also gives a lot of
> detail on 3.0 features backported to 2.6 and incompatible features
> that raise warnings in 3.0
> PEP 3000, PEP 3100 and PEP 3099 are also well worth reviewing.
So, in summary, despite the appearance of the "Python 3.0" page on the
wiki, there's really no single clearing-house source of Python 3.0
information that is maintained. The interested party needs to know a
half-dozen different resources to find out what's changing, and none
of the resources seems to attempt to be a single point of entry for
the interested party.
The wiki page had better be clear about that then. I'll edit it
\ “To label any subject unsuitable for comedy is to admit |
`\ defeat.” —Peter Sellers |
More information about the Python-list