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 scoder
Recipients brett.cannon, eric.snow, ncoghlan, pitrou, python-dev, scoder, superluser
Date 2017-06-26.21:50:10
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Sorry for not responding, missed the message, it seems.

Cython has to support old-style relative imports also in Py3 because that's how the user code was originally written, using Py2-style syntax and semantics. Most Cython code has not been converted to Py3 syntax/semantics, but still needs to work in Py3.

From a user perspective, it's best to switch on "__future__.absolute_import" and use explicit relative imports (or write Py3 code), because it reduces the overhead at import time.

I'm hoping to look into multi-step module initialisation this summer. As Nick noted, this might also help with this issue.
Date User Action Args
2017-06-26 21:50:10scodersetrecipients: + scoder, brett.cannon, ncoghlan, pitrou, python-dev, eric.snow, superluser
2017-06-26 21:50:10scodersetmessageid: <>
2017-06-26 21:50:10scoderlinkissue25791 messages
2017-06-26 21:50:10scodercreate