Make imports Python 3 compatible

[ale-rt]

No description provided.

[mgedmin]

LGTM.

Are there other fixes required for Python 3 compatibility? Because if not, then I'd like .travis.yml to start testing Python 3, and also setup.py to include the Python version classifiers.

[ale-rt]

Actually this one is already testable vs Python 3 (I just add to update the bootstrap and drop zope.testing):

[ale@emily z3c.objpath]$ python3 -m venv .
[ale@emily z3c.objpath]$ ./bin/python3 bootstrap.py 
ez_setup.py is deprecated and when using it setuptools will be pinned to 33.1.1 since it's the last version that supports setuptools self upgrade/installation, check https://github.com/pypa/setuptools/issues/581 for more info; use pip to install setuptools
Downloading https://pypi.io/packages/source/s/setuptools/setuptools-33.1.1.zip
Extracting in /tmp/tmpf3hmred_
Now working in /tmp/tmpf3hmred_/setuptools-33.1.1
Building a Setuptools egg in /tmp/bootstrap-oeu94m1q
warning: no files found matching '*' under directory 'setuptools/_vendor'
/tmp/bootstrap-oeu94m1q/setuptools-33.1.1-py3.6.egg
no previously-included directories found matching 'doc'
no previously-included directories found matching 'old-tutorial'
Creating directory '/home/ale/Code/plone/plone3/src/z3c.objpath/develop-eggs'.
Generated script '/home/ale/Code/plone/plone3/src/z3c.objpath/bin/buildout'.
[ale@emily z3c.objpath]$ ./bin/buildout -Nt 2
Setting socket time out to 2 seconds.
Develop: '/home/ale/Code/plone/plone3/src/z3c.objpath/.'
/home/ale/Code/plone/plone3/src/z3c.objpath/lib/python3.6/site-packages/setuptools/dist.py:333: UserWarning: Normalizing '1.2dev' to '1.2.dev0'
  normalized_version,
Uninstalling devpython.
Uninstalling test.
Installing test.
Generated script '/home/ale/Code/plone/plone3/src/z3c.objpath/bin/test'.
Installing devpython.
Generated interpreter '/home/ale/Code/plone/plone3/src/z3c.objpath/bin/devpython'.
[ale@emily z3c.objpath]$ ./bin/test 
Running zope.testrunner.layer.UnitTests tests:
  Set up zope.testrunner.layer.UnitTests in 0.000 seconds.
  Ran 1 tests with 0 failures, 0 errors and 0 skipped in 0.002 seconds.
Tearing down left over layers:
  Tear down zope.testrunner.layer.UnitTests in 0.000 seconds.

I think I do not have the power to add the travis hook. Can somebody do that for me please?
Can I already merge this one?

[jamadden]

Travis is enabled for z3c.objpath.

[mgedmin]

Can you push another commit so we can see Travis working? E.g. rename *.txt to *.rst for prettier ReST rendering.

[ale-rt]

Thanks @jamadden!
I will now add a travis conf file

[ale-rt]

I merged this one, thanks for caring.
To you think something else is needed before we have another PyPI release?

[mgedmin]

Personally, I'd explicitly declare all supported minor Python versions in setup.py, add Python 3.4 and 3.5 to .travis.yml, and rename *.txt to *.rst before making a new release, to bring z3c.objpath to the standard of other maintained zopefoundation packages.

(I'd also add a tox.ini for my own personal convenience, because I prefer running tox locally instead of waiting for Travis results to come in.)

But the main thing is to contact one of the current PyPI owners (hi @faassen, @witsch!) and ask them if they can make the release or add you (or anybody else who might volunteer for this duty) as a package owner on PyPI. (Oh, and add url='https://github.com/zopefoundation/z3c.objpath' to setup.py metadata.)

Oh, when asking for PyPI permissions it's best to explicitly mention your PyPI username (mine is mgedmin).

[ale-rt]

@mgedmin your plan looks reasonable, I will try to put it in practice.

BTW I am alert on PyPI (https://pypi.org/user/alert/)