Message108011
| Author |
alexhsamuel |
| Recipients |
alexhsamuel, benjamin.peterson, mark.dickinson, nascheme |
| Date |
2010年06月17日.13:04:13 |
| SpamBayes Score |
4.5279103e-07 |
| Marked as misclassified |
No |
| Message-id |
<4C1A1D4A.4090200@alexsamuel.net> |
| In-reply-to |
<1276778419.67.0.700224218468.issue9011@psf.upfronthosting.co.za> |
| Content |
How about saving the original value of STR(pnum) and restoring it after
calling ast_for_atom()?
This is not thread-safe, but I don't understand Python's threading model
well enough to know whether the GIL is held in this function.
On 6/17/2010 8:40 AM, Mark Dickinson wrote:
>
> Mark Dickinson<dickinsm@gmail.com> added the comment:
>
> Fixed in r82043 (py3k) and r82044 (release31-maint), simply by removing the relevant 'if' block.
>
> For 2.x, Antoine (on IRC) pointed out that there might well be third party code that depends on -0x80000000 being an int rather than a long (32-bit machine), so changing that behaviour could cause breakage.
>
> Can anyone propose a fix that doesn't change behaviour?
>
> ----------
>
> _______________________________________
> Python tracker<report@bugs.python.org>
> <http://bugs.python.org/issue9011>
> _______________________________________ |
|