Access to the Python results is currently down, but has anyone
actually accessed the Coverity scan results any time recently? Or who
even has access anymore?
Hi all,
If you have a few free minutes, would you mind filling out a couple of
questions? I'm giving a talk at PyCon about core development [0] and wanted
to sprinkle in some info about the people doing the work.
https://spreadsheets.google.com/viewform?formkey=dEZXWVhQMnBGREU0TUl0TTRTWk…
Feel free to answer or skip any questions. Your name isn't associated with
it.
Thanks a lot for your time, and I look forward to seeing any of you at
PyCon!
Brian
[0] http://us.pycon.org/2011/schedule/presentations/7/
It says they are "highly discouraged" because "absolute imports are
more portable and usually more readable", but now that people have had
a chance to use explicit relative imports, do people still believe
this? I mean if we truly believed this then why did we add the syntax?
I know I have used it and love it, let alone that I don't buy the
portability argument.
Am 24.02.2011 02:39, schrieb Brett Cannon:
> Not sure if Martin is the only person who can fix this, but it would be
> nice to have those URLs working.
I have added a redirect for 3.2.x. I haven't added one for 3.2.0, since
we currently don't have any redirects for X.Y.0, only for X.Y.
Regards,
Martin
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?
Georg
On behalf of the Python development team, I'm delighted to announce
Python 3.2 final release.
Python 3.2 is a continuation of the efforts to improve and stabilize the
Python 3.x line. Since the final release of Python 2.7, the 2.x line
will only receive bugfixes, and new features are developed for 3.x only.
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.
Development efforts concentrated on the standard library and support for
porting code to Python 3. Highlights are:
* numerous improvements to the unittest module
* PEP 3147, support for .pyc repository directories
* PEP 3149, support for version tagged dynamic libraries
* PEP 3148, a new futures library for concurrent programming
* PEP 384, a stable ABI for extension modules
* PEP 391, dictionary-based logging configuration
* an overhauled GIL implementation that reduces contention
* an extended email package that handles bytes messages
* a much improved ssl module with support for SSL contexts and certificate
hostname matching
* a sysconfig module to access configuration information
* additions to the shutil module, among them archive file support
* many enhancements to configparser, among them mapping protocol support
* improvements to pdb, the Python debugger
* countless fixes regarding bytes/string issues; among them full support
for a bytes environment (filenames, environment variables)
* many consistency and behavior fixes for numeric operations
For a more extensive list of changes in 3.2, see
http://docs.python.org/3.2/whatsnew/3.2.html
To download Python 3.2 visit:
http://www.python.org/download/releases/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)
I'll be mostly away from internet for Thursday and Friday,
so if any release-critical issues pop up, please don't be
surprised if I don't react promptly. I'll be back on Saturday,
to sort out any remaining issues, and the release will be
done on Sunday.
Georg
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On behalf of the Python development team, I'm happy to announce
the third release candidate of Python 3.2.
Python 3.2 is a continuation of the efforts to improve and stabilize the
Python 3.x line. Since the final release of Python 2.7, the 2.x line
will only receive bugfixes, and new features are developed for 3.x only.
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.
Development efforts concentrated on the standard library and support for
porting code to Python 3. Highlights are:
* numerous improvements to the unittest module
* PEP 3147, support for .pyc repository directories
* PEP 3149, support for version tagged dynamic libraries
* PEP 3148, a new futures library for concurrent programming
* PEP 384, a stable ABI for extension modules
* PEP 391, dictionary-based logging configuration
* an overhauled GIL implementation that reduces contention
* an extended email package that handles bytes messages
* a much improved ssl module with support for SSL contexts and certificate
hostname matching
* a sysconfig module to access configuration information
* additions to the shutil module, among them archive file support
* many enhancements to configparser, among them mapping protocol support
* improvements to pdb, the Python debugger
* countless fixes regarding bytes/string issues; among them full support
for a bytes environment (filenames, environment variables)
* many consistency and behavior fixes for numeric operations
For a more extensive list of changes in 3.2, see
http://docs.python.org/3.2/whatsnew/3.2.html
To download Python 3.2 visit:
http://www.python.org/download/releases/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)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iEYEARECAAYFAk1YzkAACgkQN9GcIYhpnLAggwCfQ92djMinrmNkGI4Ma3VRqrcX
EWIAn16kTEJtvEH/7DJApp7YdhnmIRBd
=NJ1B
-----END PGP SIGNATURE-----