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 outside in Python.exe (which does
not) results in the outputs from the tools calling out to these 32 bit
libraries to produce different outputs because the amount of data they are able
to allocate and process at the same time. The same Python script that gives
correct output on a large dataset in this desktop app will not yield the same
quality of results when run overnight as a stand-alone Python script.
Essentially this discounts Python scripts as an option for automation in this
case.
I understand that yes, applications still cannot allocate more CONTIGUOUS
memory, but this is not a regression if it continues to be so. Allowing the
process to allocate more TOTAL memory is a net benefit, especially on on
complex software systems that can't simply be rebuilt in 64 bit mode due to
third-party restraints (tied to a specific library version, lack of access to
source, lengthy software approvals processes, etc.)
--
___
Python tracker
<http://bugs.python.org/issue1449496>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
