Re: [Python-Dev] Strange error importing a Pickle from 2.7 to 3.2
Alexander Belopolsky wrote: On Wed, Feb 23, 2011 at 6:32 PM, M.-A. Lemburg m...@egenix.com wrote: Alexander Belopolsky wrote: .. In what sense is Latin-1 the official name? The IANA charset registry has the following listing Name: ISO_8859-1:1987[RFC1345,KXS2] MIBenum: 4 Source: ECMA registry Alias: iso-ir-100 Alias: ISO_8859-1 Alias: ISO-8859-1 (preferred MIME name) Alias: latin1 .. Latin-1 is short for Latin Alphabet No. 1 and started out as ECMA-94 in 1985 and 1986: This does not explain your preference of Latin-1 over Latin1. This is not my preference. See e.g. Wikipedia http://en.wikipedia.org/wiki/ISO/IEC_8859-1 It is common practice to replace spaces in descriptive names with a hyphen to come up with an identifier string (even Google does or undoes this when searching the net). Replacing spaces with an empty string is also an option, but doesn't read as well. Both are perfectly valid abbreviations for Latin Alphabet No. 1. The spelling without - has the advantage of being a valid Python identifier and a module name. The hyphens are converted to underscores by the lookup function in the encodings package. That turns the name into a valid Python module name. The IANA registration for latin1 and lack of that for latin-1 most likely indicates that the former is more commonly found in machine readable metadata. I don't know why you emphasize so much on machine readable metadata. Python source code is machine readable, the Internet is machine readable, all documents found there are machine readable. As I said earlier on: the IANA registry is just that - a registry of names with the purpose of avoiding name clashes in the resp. name space. As such, it is not a standard, but merely a tool to map various aliases to a canoncial name. The fact that an alias is registered doesn't allow any implication on whether it's in wide-spread use or not, e.g. csISOLatin1 gives me 6810 hits on Google. I get 788,000 hits for 'latin1 -latin-1' on Google, 'latin-1' gives 2,600,000 hits. Looks like it's still the preferred way to write that encoding name. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Source (#1, Feb 24 2011) Python/Zope Consulting and Support ...http://www.egenix.com/ mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/ mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/ ::: Try our new mxODBC.Connect Python Database Interface for free ! eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Strange error importing a Pickle from 2.7 to 3.2
On 2/24/2011 4:02 AM, M.-A. Lemburg wrote: I get 788,000 hits for 'latin1 -latin-1' on Google, 'latin-1' gives 2,600,000 hits. Looks like it's still the preferred way to write that encoding name. That's bogus. You can't search for latin-1 on Google, it isn't strict enough. The third hit is a url containing latin1 and a title of Latin 1. And it picks up things like Latin 1: The Easy Way, which is a book on Latin. However, you *can* search much more strictly on Google Code Search, which gives 4,014 (latin-1) to 13,597 (latin1). http://www.google.com/codesearch?hl=enlr=q=%28\%22latin1\%22|\%27latin1\%27%29sbtn=Search http://www.google.com/codesearch?hl=enlr=q=%28\%22latin-1\%22|\%27latin-1\%27%29sbtn=Search So, no, I don't think the development world aligns with your pedantry. That's not to say this is a popularity contest, but then let's not cite google hit counts as proof. -- Scott Dial sc...@scottdial.com scod...@cs.indiana.edu ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Link to issue tracker
On Wed, Feb 23, 2011 at 22:43, Martin v. Löwis mar...@v.loewis.de wrote: What redirect.txt did you edit specifically? It was beta.python.org/build/redirects.txt http://beta.python.org/build/redirects.txt, but I went ahead and reverted the change since your solution works. Ah. That file isn't used, AFAICT, so I now deleted it. Are you sure? I added entries last week to that file and they worked when the website updated. If there are any other redirects that you want to see active, please let me know. Personally I cared about all of the redirects that were in that file pertaining to /dev. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r88501 - python/branches/py3k/Lib/smtplib.py
Mmmm probably. smtplib patches aren't too big/many though. Should I revert the change? 2011/2/23 Georg Brandl g.bra...@gmx.net: You're sure this will not cause tedious conflicts with backports? Georg On 22.02.2011 16:56, giampaolo.rodola wrote: Author: giampaolo.rodola Date: Tue Feb 22 16:56:20 2011 New Revision: 88501 Log: smtlib.py PEP8 normalization via pep8.py script. Modified: python/branches/py3k/Lib/smtplib.py Modified: python/branches/py3k/Lib/smtplib.py == --- python/branches/py3k/Lib/smtplib.py (original) +++ python/branches/py3k/Lib/smtplib.py Tue Feb 22 16:56:20 2011 @@ -52,15 +52,15 @@ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/g.rodola%40gmail.com ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r88501 - python/branches/py3k/Lib/smtplib.py
On 24.02.2011 20:51, Giampaolo Rodolà wrote: Mmmm probably. smtplib patches aren't too big/many though. Should I revert the change? It's probably fine if you do the same change to the maintenance branches as well. Georg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] r88501 - python/branches/py3k/Lib/smtplib.py
Done for Python 3.1 and 2.7. 2011/2/24 Georg Brandl g.bra...@gmx.net: On 24.02.2011 20:51, Giampaolo Rodolà wrote: Mmmm probably. smtplib patches aren't too big/many though. Should I revert the change? It's probably fine if you do the same change to the maintenance branches as well. Georg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/g.rodola%40gmail.com ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [RELEASED] Python 3.2
On 23.02.2011 23:45, Barry Warsaw wrote: On Feb 21, 2011, at 12:39 AM, Victor Stinner wrote: Le dimanche 20 février 2011 à 23:22 +0100, Georg Brandl a écrit : 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. Congratulation to all Python developers for this wonderful release! And a special kudo to our release manager, Georg. Indeed, great job Georg. I hereby nominate you for Python 3.3 RM. No good deed goes unpunished. :) Well, I guess that makes sense. In a twisted way :) Georg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] [issue11286] Some trivial python 2.x pickles fails to load in Python 3.2
It seems appropriate to consult python-dev on this. I thought ValueError was for values that are valid Python objects but out of acceptable range of the function. Errors that can only be triggered in C code normally handled with either assert() or raise SystemError. I think you are splitting hairs too thin by distinguishing between stdlib and 3rd party extensions. On Thu, Feb 24, 2011 at 4:07 PM, Antoine Pitrou rep...@bugs.python.org wrote: Antoine Pitrou pit...@free.fr added the comment: I've committed the part of the patch which disallows a NULL data pointer with PyMemoryView_FromBuffer in r88550 and r88551. Is it possible to create such buffer in Python (other than by exploiting a bug or writing a rogue extension module)? If not, this should be a SystemError or even just an assert() rather than ValueError. I'm against asserts for such use, since they get disabled in non-debug mode (which is the mode 99.99% of users run in). As for SystemError, it means Internal error in the Python interpreter, which isn't the case here (most likely it's an error in an extension module instead, possibly a third-party one). -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue11286 ___ ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Mercurial conversion repositories
Hello, Georg and I have been working on converting the SVN repository to Mercurial. We can now present you a test repository (actually, two). CPython repository: http://hg.python.org/cpython/ -- This is the main conversion repository. It contains all history of trunk and py3k (since 1990!) up to now, including all maintenance branches starting from 2.0 up to 3.2. If you are a core developer, get your local clone of the repository using: $ hg clone ssh://h...@hg.python.org/cpython (this uses the same SSH key as your Subversion access; for more information about Mercurial and SSH keys, see the converted development FAQ: http://potrou.net/hgdevguide/faq.html#faq ) If you are not a core developer: $ hg clone http://hg.python.org/cpython Your clone will contain the following branches: $ hg branches default68026:f12ef116dd10 3.268025:cef92ee1a323 2.768010:8174d00d0797 3.167955:5be8b695ea86 2.667287:5e26a860eded 2.565464:e4ecac76e499 trunk 62750:800f6c92c3ed 3.060075:1d05144224fe 2.458552:df72cac1899e 2.345731:a3d9a9730743 2.240444:d55ddc8c8501 2.130171:06fcccf6eca8 2.018214:dc0dfc9565cd The branch default is the current py3k branch from SVN. The branch trunk represents SVN trunk history until 2.7 was branched for maintenance. The full list of tags is too long to print here, but you can get it using: $ hg tags The size of the repository on-disk is (depending on your filesystem): $ du -hs .hg 176M.hg (the size of the network transfer is estimated to be around 80MB) You can commit and even push to this repository (the latter if you are a core developer). Since this is a test repository, whatever you push will be discarded when we do the final conversion. CPython with extra history: http://hg.python.org/cpythonextrahist/ -- This repository is bigger, and has a much more complicated topology. It is a superset of the other repository, and contains the totality of the branches from the SVN repository (it has more than 450 repository heads, of which 87 non-closed). It also weighs quite a bit more: $ du -hs .hg 248M.hg This repository is unnecessary for development work, since even for history-digging purposes the normal repository has the necessary information. This repository is only to preserve historical record of some of the non-trunk development work from the SVN repository (such as orphaned/deleted feature branches). Development guide: http://potrou.net/hgdevguide/ - This is the development guide adapted for Mercurial. You can get its sources from the branch hg_transition in http://hg.python.org/devguide/. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial conversion repositories
On Feb 24, 2011, at 4:19 PM, Antoine Pitrou wrote: Georg and I have been working on converting the SVN repository to Mercurial. We can now present you a test repository (actually, two). CPython repository: http://hg.python.org/cpython/ Thank you both for all the effort you put in. I'll do some tests today. Raymond ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial conversion repositories
On Thu, Feb 24, 2011 at 16:19, Antoine Pitrou solip...@pitrou.net wrote: Hello, Georg and I have been working on converting the SVN repository to Mercurial. We can now present you a test repository (actually, two). Thanks to the both of you for moving this forward! CPython repository: http://hg.python.org/cpython/ -- This is the main conversion repository. It contains all history of trunk and py3k (since 1990!) up to now, including all maintenance branches starting from 2.0 up to 3.2. If you are a core developer, get your local clone of the repository using: $ hg clone ssh://h...@hg.python.org/cpython (this uses the same SSH key as your Subversion access; for more information about Mercurial and SSH keys, see the converted development FAQ: http://potrou.net/hgdevguide/faq.html#faq ) If you are not a core developer: $ hg clone http://hg.python.org/cpython Your clone will contain the following branches: $ hg branches default68026:f12ef116dd10 3.268025:cef92ee1a323 2.768010:8174d00d0797 3.167955:5be8b695ea86 2.667287:5e26a860eded 2.565464:e4ecac76e499 trunk 62750:800f6c92c3ed 3.060075:1d05144224fe 2.458552:df72cac1899e 2.345731:a3d9a9730743 2.240444:d55ddc8c8501 2.130171:06fcccf6eca8 2.018214:dc0dfc9565cd The branch default is the current py3k branch from SVN. The branch trunk represents SVN trunk history until 2.7 was branched for maintenance. Just to help justify it in my head, the trunk branch exists for the history and nothing more, right? I mean we are not even accepting commits on it after we branched so I assume there is no real new history there compared to 2.7. Could we actually close the branch so it isn't even visible by default to prevent confusing people? -Brett The full list of tags is too long to print here, but you can get it using: $ hg tags The size of the repository on-disk is (depending on your filesystem): $ du -hs .hg 176M.hg (the size of the network transfer is estimated to be around 80MB) You can commit and even push to this repository (the latter if you are a core developer). Since this is a test repository, whatever you push will be discarded when we do the final conversion. CPython with extra history: http://hg.python.org/cpythonextrahist/ -- This repository is bigger, and has a much more complicated topology. It is a superset of the other repository, and contains the totality of the branches from the SVN repository (it has more than 450 repository heads, of which 87 non-closed). It also weighs quite a bit more: $ du -hs .hg 248M.hg This repository is unnecessary for development work, since even for history-digging purposes the normal repository has the necessary information. This repository is only to preserve historical record of some of the non-trunk development work from the SVN repository (such as orphaned/deleted feature branches). Just to give a comparison to svn, release-27maint is 243M and py3k is 231M (and that is with `make distclean` run). IOW the complete history of all branches of Python is just 5M bigger than just a checkout of 2.7. -Brett Development guide: http://potrou.net/hgdevguide/ - This is the development guide adapted for Mercurial. You can get its sources from the branch hg_transition in http://hg.python.org/devguide/. Regards Antoine. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/brett%40python.org ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial conversion repositories
On Fri, Feb 25, 2011 at 02:19, Antoine Pitrou solip...@pitrou.net wrote: Hello, Georg and I have been working on converting the SVN repository to Mercurial. We can now present you a test repository (actually, two). CPython repository: http://hg.python.org/cpython/ -- This is the main conversion repository. It contains all history of trunk and py3k (since 1990!) up to now, including all maintenance branches starting from 2.0 up to 3.2. If you are a core developer, get your local clone of the repository using: $ hg clone ssh://h...@hg.python.org/cpython (this uses the same SSH key as your Subversion access; for more information about Mercurial and SSH keys, see the converted development FAQ: http://potrou.net/hgdevguide/faq.html#faq ) Yay - Mercurial at last! Thanks for pushing this forward. I'll do some tests with the new repo later today. Eli ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial conversion repositories
On 25.02.2011 01:19, Antoine Pitrou wrote: Hello, Georg and I have been working on converting the SVN repository to Mercurial. We can now present you a test repository (actually, two). The implied agenda is that we would be *very* happy if we could do the final conversion during PyCon (we both won't be attending, so we have plenty of time ;) -- so that the sprints can already benefit from the agility provided by hg. That's a timescale of around two weeks, which should be plenty for testing. CPython repository: http://hg.python.org/cpython/ -- This is the main conversion repository. It contains all history of trunk and py3k (since 1990!) up to now, including all maintenance branches starting from 2.0 up to 3.2. If you are a core developer, get your local clone of the repository using: $ hg clone ssh://h...@hg.python.org/cpython (this uses the same SSH key as your Subversion access; for more information about Mercurial and SSH keys, see the converted development FAQ: http://potrou.net/hgdevguide/faq.html#faq ) [...] You can commit and even push to this repository (the latter if you are a core developer). Since this is a test repository, whatever you push will be discarded when we do the final conversion. So, to stress this point: Please *do* experiment, commit and push stuff to this repository, especially if you've not worked with hg before. You can break nothing (or if you do, it's not your fault :) Georg ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] strange buildbot fail
Hi, Earlier today I've committed revision 88554, and a bit later a buildbot failure message was received: Builder AMD64 Windows Server 2008 hg-3.x build #47 failed with failed test_import, blamelist having my name because I made the last commit (apparently). Two other buildbots succeeded building and testing after my commit, as did my local tests. Some examination of the failed test shows no apparent connection to my commit. What can be done in cases like this? How to investigate further? Thanks in advance, Eli ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Mercurial conversion repositories
On Fri, Feb 25, 2011 at 01:19, Antoine Pitrou solip...@pitrou.net wrote: Georg and I have been working on converting the SVN repository to Mercurial. We can now present you a test repository (actually, two). Sorry everyone for taking so long on the conversion. Looks like Antoine and Georg have more time and energy to spend on this than I do, so I will let them pick up my slack. Cheers, Dirkjan ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
