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 mark.dickinson
Recipients Kiriakos.Vlahos, eric.smith, mark.dickinson, sjmachin
Date 2010-09-29.15:15:03
SpamBayes Score 1.7272901e-08
Marked as misclassified No
Message-id <1285773305.61.0.85802985782.issue9980@psf.upfronthosting.co.za>
In-reply-to
Content
> The puzzling thing is that the same Python.dll when used by python.exe and not PyScripter produces correct results.

Yes, this is indeed puzzling.  Are you absolutely sure that both python.exe and PyScripter are using the exact same Python.dll file?  E.g., can you check that renaming/deleting/moving the Python.dll file to somewhere else causes both python.exe and PyScripter to fail to execute?

I really can't think of anything in the environment which might affect whether this bug occurs or not.

It's difficult to proceed here without a concrete way to reproduce the error.  I can (and will) add the particular bad values you found as new testcases, so that if the error is present on any of the buildbots it'll show up.
History
Date User Action Args
2010-09-29 15:15:05mark.dickinsonsetrecipients: + mark.dickinson, sjmachin, eric.smith, Kiriakos.Vlahos
2010-09-29 15:15:05mark.dickinsonsetmessageid: <1285773305.61.0.85802985782.issue9980@psf.upfronthosting.co.za>
2010-09-29 15:15:03mark.dickinsonlinkissue9980 messages
2010-09-29 15:15:03mark.dickinsoncreate