➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients Jason.Scheirer, amaury.forgeotdarc, brian.curtin, gfe, josiahcarlson, loewis, pitrou, tim.golden, tim.peters
Date 2010-12-18.02:52:59
SpamBayes Score 4.7279376e-05
Marked as misclassified No
Message-id <4D0C220A.8090906@v.loewis.de>
In-reply-to <1292626590.62.0.611321018155.issue1449496@psf.upfronthosting.co.za>
Content 
> I would like to see this reopened: we have a very large class of
> users that are not ready to entirely port to 64-bit and need this
> now.

And I remain -1 to such requests. You can appeal to that by writing a
PEP, or finding a committer who is willing to make this change.

Alternatively, just provide these users with binaries that you built
yourself, or hire somebody to build such binaries for you.

> I understand that yes, applications still cannot allocate more
> CONTIGUOUS memory, but this is not a regression if it continues to be
> so. 

It would be a regression if Python started crashing because of that
change, which is my concern.
History
Date User Action Args
2010-12-18 02:53:02loewissetrecipients: + loewis, tim.peters, josiahcarlson, amaury.forgeotdarc, pitrou, gfe, tim.golden, brian.curtin, Jason.Scheirer
2010-12-18 02:52:59loewislinkissue1449496 messages
2010-12-18 02:52:59loewiscreate