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 alexandre.vassalotti
Recipients alexandre.vassalotti, christian.heimes, gvanrossum
Date 2007-10-14.01:32:10
SpamBayes Score 0.003061149
Marked as misclassified No
Message-id <1192325530.75.0.439779829904.issue1272@psf.upfronthosting.co.za>
In-reply-to
Content
Guido wrote:
> I figured out the problem -- it came from marshalled old code objects. 
> If you throw away all .pyc files the problem goes away.  You can also
> get rid of the similar checks for the 'name' argument -- this should
> just be a PyUnicode too.  A systematic approach to invalidating all the
> .pyc files is updating the magic number in import.c.

Done.

I had to remove a few another PyString instances in pyexpat.c and
_ctypes.c. So, here (hopefully) the final version of the patch. 

The changes from the last version are:

   - Correct a typo in of the comments in PyUnicode_DecodeFSDefault
   - Specified in the API doc of PyUnicode_DecodeFSDefault that the
     function take a null-terminated string.
   - Bumped the magic number in import.c
   - Fix PyCode_New calls in _ctypes and pyexpat module.
   - Remove the PyString type check on 'filename' and 'name' in PyCode_New.
   - Remove the unneeded string coercion code from PyCode_New.
Files
File name Uploaded
updated_file_fsenc-2.patch alexandre.vassalotti, 2007-10-14.01:32:10
History
Date User Action Args
2007-10-14 01:32:11alexandre.vassalottisetspambayes_score: 0.00306115 -> 0.003061149
recipients: + alexandre.vassalotti, gvanrossum, christian.heimes
2007-10-14 01:32:10alexandre.vassalottisetspambayes_score: 0.00306115 -> 0.00306115
messageid: <1192325530.75.0.439779829904.issue1272@psf.upfronthosting.co.za>
2007-10-14 01:32:10alexandre.vassalottilinkissue1272 messages
2007-10-14 01:32:10alexandre.vassalotticreate