[issue1551] Port Python/import.c to py3k branch

Christian Heimes added the comment: Thanks! I manually fixed several of the PyString -> PyUnicode differences but it didn't work for me. Maybe I missed one or two places. Anyway the main issue is sovled. :] __ Tracker <[EMAIL PROTECTED]>

[issue1551] Port Python/import.c to py3k branch

Nick Coghlan added the comment: I should have known that fiddling with import.c couldn't possibly go as smoothly as it had been ;) The problem actually turned out to be fairly shallow - the merge picked up a lot of calls to the PyString_* interfaces from the 2.x import implementation. Replacing

[issue1551] Port Python/import.c to py3k branch

New submission from Christian Heimes: Dear Nick! I wasn't able to get your modification to Python/import.c from r59288 to run. Can you please port the files to py3k yourself? Thanks! Christian -- assignee: ncoghlan components: Interpreter Core keywords: py3k messages: 58155 nosy: ncogh