[issue1449496] Python should use 3GB Address Space on Windows

Chad Austin added the comment: IMVU's downloadable client is built atop CPython. 80% of our users use 32-bit Windows and 20% use 64-bit Windows. We do not intend to provide 64-bit builds of our application for many of the same reasons sketched out in http://blogs.msdn.com/b/ricom/archive/20

[issue1449496] Python should use 3GB Address Space on Windows

Martin v. Löwis added the comment: > 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 ma

[issue1449496] Python should use 3GB Address Space on Windows

Antoine Pitrou added the comment: > When running a Python script from within a desktop application (which > embeds Python and has /LARGEADDRESSAWARE set) [...]. Essentially this > discounts Python scripts as an option for automation in this case. Well, if you already embed Python in your applic

[issue1449496] Python should use 3GB Address Space on Windows

Jason Scheirer added the comment: 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. When running a Python script from within a desktop application (which embeds Python and has /LARGEADDRESSAWARE set) or outs

[issue1449496] Python should use 3GB Address Space on Windows

Amaury Forgeot d'Arc added the comment: > What is 64-bit safe should be 32-bit safe, not only 31-bit safe Not here. Python uses "signed size_t" for various lengths and sizes. On win32 this only gives you 31 bits... -- nosy: +amaury.forgeotdarc ___ P

[issue1449496] Python should use 3GB Address Space on Windows

Martin Gfeller Martin Gfeller added the comment: Martin, we're running with this for years and with many extensions modules, without an issue. What is 64-bit safe should be 32-bit safe, not only 31-bit safe. But you're right, this is not a proof, and we have switched

[issue1449496] Python should use 3GB Address Space on Windows

Martin v. Löwis added the comment: I'm rejecting this as "won't fix". Users having the underlying problem (i.e. need more than 2GB of heap) really should switch to a 64-bit installation. The risk of something breaking is just not worth it. That testing showed no issues is not convincing at al

[issue1449496] Python should use 3GB Address Space on Windows

Changes by Antoine Pitrou : -- stage: unit test needed -> versions: +Python 3.2 -Python 2.7, Python 3.1 ___ Python tracker ___ ___

[issue1449496] Python should use 3GB Address Space on Windows

Changes by Antoine Pitrou : -- nosy: +loewis, tim.golden ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue1449496] Python should use 3GB Address Space on Windows

Jason Scheirer added the comment: The patch is a simple tweak to the Visual Studio project's compiler settings. Seems quite innocuous, nothing broke in the Python harness or our internal harnesses (at ESRI) by enabling this. -- keywords: +patch nosy: +Jason.Scheirer status: pending ->

[issue1449496] Python should use 3GB Address Space on Windows

Brian Curtin added the comment: Unless anyone plans on a patch I say we let this go. As of 2.5 we provide x64 installers, and with most users running on 64-bit OS'es I would say it's better to suggest they use a 64-bit compiled Python to obtain an even larger addressable space. Of course, no

[issue1449496] Python should use 3GB Address Space on Windows

Changes by Daniel Diniz : -- stage: -> test needed versions: +Python 2.7, Python 3.1 ___ Python tracker ___ ___ Python-bugs-list ma