News for hackers. Stuff that matters.
Re:Python 3.3 reintroduces explicit Unicode literals to ease... by kibwen on Friday March 16, 2012 @04:25PM (#3715121)
Won't be backported (which would be sort of weird in any case... if you were going to actually go to the trouble of upgrading your copy of 3.2 by a minor version, you might as well just upgrade to 3.3), but they do address this in the PEP:

  There are many existing Python communities that are prepared to put 
  up with the constraints imposed by the existing suite of porting 
  tools, or to update their Python 2 code bases sufficiently that the 
  problems are minimised.

  This PEP is not for those communities. Instead, it is designed 
  specifically to help people that don't want to put up with those 
  difficulties.

  However, since the proposal is for a comparatively small tweak to 
  the language syntax with no semantic changes, it is feasible to 
  support it as a third party import hook. While such an import hook 
  imposes some import time overhead, and requires additional steps 
  from each application that needs it to get the hook in place, it 
  allows applications that target Python 3.2 to use libraries and 
  frameworks that would otherwise only run on Python 3.3+ due to their 
  use of unicode literal prefixes.

  One such import hook project is Vinay Sajip's uprefix [4].

  For those that prefer to translate their code in advance rather than 
  converting on the fly at import time, Armin Ronacher is working on a 
  hook that runs at install time rather than during import [5].

  Combining the two approaches is of course also possible. For 
  example, the import hook could be used for rapid edit-test cycles 
  during local development, but the install hook for continuous 
  integration tasks and deployment on Python 3.2.

  The approaches described in this section may prove useful, for 
  example, for applications that wish to target Python 3 on the Ubuntu 
  12.04 LTS release, which will ship with Python 2.7 and 3.2 as 
  officially supported Python versions.
Re:Python 3.3 reintroduces explicit Unicode literals to ease... by maaku on Friday March 16, 2012 @04:37PM (#3715165)
It's not so simple. As mentioned in the last paragraph, for example, Ubuntu LTS will release with Python 3.2. Backporting this feature to 3.2 will make it available to (updated and patched) Ubuntu LTS installs. NOT backporting this PEP could result in further delays in Python 3 adoption as people wait for Ubuntu 14.04 LTS.
Re:Python 3.3 reintroduces explicit Unicode literals to ease... by kibwen on Friday March 16, 2012 @05:04PM (#3715276)
A good point. I do wonder what proportion of Ubuntu users take advantage of the LTS releases rather than, say, just outright using Debian. I also intuitively want to say that anyone deciding to go with a LTS release would, if given the choice between a 2.7 library and a 3.2 library, choose the more "mature" option anyway.

I agree that it would have been smart to backport such a seemingly small and unobtrusive change to 3.2 (and who knows, maybe they still will).

Re:Python 3.3 reintroduces explicit Unicode literals to ease... by kibwen on Friday March 16, 2012 @06:19PM (#3715568)
Actually, no, after contemplation I realize that it would be much worse to split the compatibility of 3.2 and force library authors to qualify their compatibility targets by the minor version. After all, if the hypothetical 3.2.new didn't require any porting effort to support 3.3-style unicode literals, then library authors would have even less incentive to port their libraries to 3.2.old for all the people who can't upgrade, or won't upgrade, or who don't realize that their version doesn't feature a critical language addition.
Re:Python 3.3 reintroduces explicit Unicode literals to ease... by andrewcooke on Friday March 16, 2012 @08:08PM (#3715888)
in my experience, people (and distros) will update minor versions in mid-life patches/updates. so backporting gets this fix to "legacy" installs, where a new python version is not acceptable (i have clients with python 2.5 - 5 years from now the same kinds of people will be stuck on 3.1).

and i'm not sure why comparing three digits rather than two is so much more difficult. can you expand on your logic there?

Re:Python 3.3 reintroduces explicit Unicode literals to ease... by kibwen on Saturday March 17, 2012 @12:58AM (#3716408)

  > and i'm not sure why comparing three digits rather than two is so much more difficult. can you expand on your logic there?
Really only because it defies what people are used to. I really shouldn't have referred to that third number as the "minor version number", perhaps "the bugfix version number" would have been more appropriate, as that's what people (broadly speaking) expect it to stand for.

I acknowledge that there are arguments to be made for both viewpoints. However, I don't think that the risk of slightly delaying adoption of Python 3k due to concerns of a "compatibility hole" with Python 3.2 are worth introducing even more version chaos into the Python ecosystem. (You could just as easily argue that this move would prevent version chaos by eradicating the compatibility hole, but there will always those people who will forever be stuck on 3.2.old, for whatever reason.) I could be wrong! But regardless of what I think, the fact that the preceding argument can even be raised seems to indicate that it would be politically untenable for the Python devteam to suggest such a course of action. As far as they're concerned, Py3k adoption is progressing at a reasonable pace (though clearly not as smoothly as they'd hoped).

Re:Python 3.3 reintroduces explicit Unicode literals to ease... by j-kidd on Saturday March 17, 2012 @12:34AM (#3716370)
Modern stack is just not compatible with Ubuntu LTS. You can either pull stuffs from ppa, build them from source, roll your own packages, or, heaven forbid, choose a better distro.