On 01/29/2016 08:41 PM, Emmanuel Bourg wrote:
>> Also, there's no separate tarball for the antlr3 Python package, it's
>> all-in-one.
> Well, couldn't the tarball of the python-antlr3 package simply consist
> in the content of the runtime/Python3 directory? Repacking the tarball
> isn't difficult. That's how the C runtime was packaged I believe
> (libantlr3c).
> Emmanuel Bourg

After some investigation, I can see it wont be easy to detach the Python
module from the rest.

The problem is that the Python bindings require the toplevel tree. See
the code in setup.py:

        rootDir = os.path.abspath(
            os.path.join(os.path.dirname(__file__), '..', '..'))

then later on the rootDir is used for the jar files.

So, yeah, I could do it, but then it will mean either heavily patching
setup.py, or not run the unit tests. Both options aren't very
satisfying, knowing that it should be very easy to add Python support in
the existing antlr3 package.

I'll try further, and I'll let you know.


Thomas Goirand (zigo)

This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to