Ross Cohen added the comment:
On Fri, 29 Jan 2010 21:15:14 +
Marc-Andre Lemburg wrote:
> Breaking existing applications and ports of Python for 2.7
> certainly won't make anything easier for anyone.
>
> For 2.7 we will certainly not allow the above to happen,
> sinc
Ross Cohen added the comment:
I am confused by this line of reasoning. Is it ok to ignore the
deprecation process in py3k but not in 2.x? Is it only ok if a core
developer does it?
If the point of 2.7 is to make it easier for apps and packages to be
ported to py3k, then what would be the point
Ross Cohen added the comment:
On Sat, 23 Jan 2010 18:23:10 +
Antoine Pitrou wrote:
> By the way, the new GIL only works with POSIX and Windows NT threading APIs.
> Perhaps it can't be backported at all to 2.x, given that 2.x supports more
> threading APIs than py3k does?
Ross Cohen added the comment:
On Fri, 22 Jan 2010 09:32:36 +
Marc-Andre Lemburg wrote:
> * Please add the fallback solutions from the time module in case
> gettimeofday() is not available. You cannot assume that "all modern POSIX
> systems" implement that API - i
Ross Cohen added the comment:
Thanks Neil for fixing up the patch.
As for Marc-Andre's comments, I'm happy to backport any further
changes which happen on the py3k branch. I'd like to keep this as a
strict backport, only changing things as necessary to get it to work
with the
New submission from Ross Cohen :
This is a backport of the newgil work to the 2.7 branch (otherwise known as
trunk.) Patch is against r77678.
Created by diffing r76193 (last in the newgil branch)
against r76189 and applying the result. Generally applied cleanly and it looked
as though only 1
