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 amdescombes
Recipients amdescombes, loewis
Date 2007-10-12.11:41:16
SpamBayes Score 0.00024097165
Marked as misclassified No
Message-id <d674db060710120441y40f01482k1c42a7c7c0bfc88f@mail.gmail.com>
In-reply-to <1192184451.36.0.525480772214.issue1270@psf.upfronthosting.co.za>
Content
Martin,

it is really a bug, as I have tried on a machine with Windows 2003 server
and 4GBs of ram and it still doesn't run, and it does run on xp with only
1GB of ram.
Does python.exe have then IMAGE_FILE_LARGE_ADDRESS_AWARE bit set, that could
explain the behaviour it its not set.

Thanks,

Andre M. Descombes

On 10/12/07, Martin v. Löwis <report@bugs.python.org> wrote:
>
>
> Martin v. Löwis added the comment:
>
> Please understand that the purpose of this bug tracker is to track bug
> reports and patches to Python, not a means of getting help in using
> Python. If you think you have found a bug, please submit a bug report
> that allows us to reproduce the bug. If you merely need help, please use
> some of the Python community channels, such as python-list@python.org.
>
> As for your question: I'm not aware of an issue with Windows 2003 server
> that could explain that behavior. Most likely, you get the MemoryError
> because you really ran out of memory. Try increasing the page file, and
> put more main memory into the machine.
>
> ----------
> nosy: +loewis
> resolution:  -> invalid
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue1270>
> __________________________________
>
Files
File name Uploaded
unnamed amdescombes, 2007-10-12.11:41:15
History
Date User Action Args
2007-10-12 11:41:16amdescombessetspambayes_score: 0.000240972 -> 0.00024097165
recipients: + amdescombes, loewis
2007-10-12 11:41:16amdescombeslinkissue1270 messages
2007-10-12 11:41:16amdescombescreate