Thanks for the quick response. Cloning the repositories then doing
python3.2 setup.py install
did indeed work for logilab-common and logilab-astng. Unfortunately, it did not
for pylint, which is what I was really after. Guess I['ll just have to wait for
you to get there. Let me know if you want to see any of my error output. It
should be pretty easy to reproduce though -- this was a fresh Python3.2
compiled from source, so there was nothing else to get in the way.
If you think pylint could be made to work with a few modest changes, I'd be
willing to take a shot at that (with a little guidance about how to approach
the effort).
On Apr 4, 2011, at 4:54 AM, Julien Jehannet wrote:
>> * Mitchell L Model <[email protected]> [03-avril-2011 19:47]:
>> I downloaded the current versions of logilab-common, logilab-astng,
>> and logilab-pylint. In each directory, I followed the instructions in
>> README.Python3 to execute:
>> find . ! -path "*/test/*py" -name "*py" -exec 2to3-3.1 -wn {} \;
>> in each directory. I then did:
>> sudo python3 setup.py install
>> in each directory (i.e., with the directory the current directory).
>
> Sorry for the inconvenience but we have no manpower at the
> moment to keep track of all the changes related to python3.
>
> But the good news are the next transition to python3.2 in Debian which
> can let us use our continuous integration tool (apycot) to detect
> failures (and to provide python3 package in sid release).
>
> However at the moment, the python3 migration should be almost "usable";
> i.e. few corrections are maybe necessary to work (patch accepted :-).
>
> I'm afraid the README.Python3 is wrong now (for logilab.common and
> logilab.astng at least) since we use the 2to3 tool directly in the
> installation
> process as advocated in http://wiki.python.org/moin/PortingPythonToPy3k
> (approach 1).
>
> So, running the install command should be enough now to launch the
> py3k compilation step:
>
> python3 setup.py install --home=/tmp
>
> I would recommend to use python3.2 instead of python3.1 in which the
> unittest module is quite inadequate to our test series.
>
>> For each of the three directories I got an immediate error:
>> Traceback (most recent call last):
>> File "setup.py", line 46, in <module>
>> from .__pkginfo__ import modname, version, license, description, \
>> ValueError: Attempted relative import in non-package
> Not reproducted here. I bet on a repo with a broken distutils build in
> the project directory. I suggest you to clone the repo and to use the "hg
> clean" command to purge all the dead files.
>
>> I understand the error, but I don't understand why it happened or how
>> to fix it. I'm sure I'm not the first person to try to install these
>> libraries for Python 3....
> Thanks for the report and I will fix the documentation in next release.
> --
> Julien JEHANNET LOGILAB, Paris
> (France)
> http://www.cubicweb.org CubicWeb, le cadriciel du web
> sémantique
> http://www.logilab.org Dépôt des logiciels libres conçus par
> Logilab
> http://www.logilab.fr Informatique scientifique & Gestion de
> connaissances
_______________________________________________
Python-Projects mailing list
[email protected]
http://lists.logilab.org/mailman/listinfo/python-projects
