C extension not used in Python 3 #4
Comments
jamadden
added a commit
that referenced
this issue
May 1, 2017
…`` the same Fixes #4 and fixes #5. Add a specific test case for both of these things. Enabling the C extension on Python 3 revealed more places where readonly attributes can raise different exceptions so fix those tests. Also add Python 3.6 to the supported list, and use zope.testrunner to workaround the namespace package issue.
jamadden
added a commit
that referenced
this issue
May 1, 2017
…`` the same Fixes #4 and fixes #5. Add a specific test case for both of these things. Enabling the C extension on Python 3 revealed more places where readonly attributes can raise different exceptions so fix those tests. Also add Python 3.6 to the supported list, and use zope.testrunner to workaround the namespace package issue.
jamadden
added a commit
that referenced
this issue
May 1, 2017
…`` the same Fixes #4 and fixes #5. Add a specific test case for both of these things. Enabling the C extension on Python 3 revealed more places where readonly attributes can raise different exceptions so fix those tests. Also add Python 3.6 to the supported list, and use zope.testrunner to workaround the namespace package issue.
clrpackages
pushed a commit
to clearlinux-pkgs/zope.i18nmessageid
that referenced
this issue
May 9, 2017
…o version 4.1.0 4.1.0 (2017-05-02) ------------------ - Drop support for Python 2.6 and 3.2. - Add support for Python 3.5 and 3.6. - Fix the C extension not being used in Python 3. See `issue 4 <https://github.com/zopefoundation/zope.i18nmessageid/issues/4>`_. - Make the Python implementation of Message accept any object for the ``default`` argument, just as the C extension does. This should be a unicode or byte string. See `issue 5 <https://github.com/zopefoundation/zope.i18nmessageid/issues/5>`_.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because the import line simply does
import _zope_i8nmessageid_message, which is absolute, and so the module con't be found.The text was updated successfully, but these errors were encountered: