Also, a new jpylyzer release is scheduled for late November. As this will be a 2.0 release with some breaking changes in the output format (relative to the 1.x releases), some users may want to stick to the 1.18 release for a while. Because of this I think it would be a good idea to fix the packaging for the current 1.18 release.
FWIW, the upstream jpylyzer source code (of which I'm the maintainer) is
already fully compatible with Python 3 (and has been since the first
jpylyzer release in 2011). If there are any Python 2 dependencies, they
are only in the current packaging (which I think should be easy to fix,
but I'm not that familiar with the package-specific code).
