at.
FYI, we (logilab) are curently working on providing a compatibility layer
between _ast and compiler to get pylint working on py3k, py >= 2.6 and py <=
2.5. There are some tree structure incompatibility between them which makes
the thing not trivial but I hope we'll get somewher
eterized query.
can't you simply use dbmodule.Binary to do the job?
--
Sylvain Thénault LOGILAB, Paris (France)
Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations
Développement logiciel sur mesure: http://www.logilab.fr/s
et.
IMO the point is that we can consider as a bug the fact that find_module
tries to somewhat read the content of the file, no? Though it seems to only
doing this for encoding detection or like since find_module doesn't choke on
a module containing another kind of syntax error.
So the questio
the full act of importing and not for just finding out if
> or where module xyz exists.
in python 2, find_module was usable for such usage, and this is a needed api
for a tool like pylint. Is there another way to do so with python 3?
--
Sylvain Thénault LOGILAB
provided a complete list of changes.
Even better, pylint sorts its messages between various categories, and
it would be as easy to get a py3k migration category so users can launch
pylint to get only migration related messages (or filter them out as
well). IMO that could be acheive in a couple of hour
, 22:33:39)
[GCC 4.5.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import package
Traceback (most recent call last):
File "", line 1, in
File "package/__init__.py", li
that far from PEP8. I would be
actually interested about what you think is not conformant, or even
which test are missing for a better "PEP8 compliance test".
--
Sylvain Thénault LOGILAB, Paris (France).
http://www.logilab.com http://www.logilab.fr htt
is not correct, and explain why and what should be done, I can
rework on it.
regards,
--
Sylvain Thénault LOGILAB, Paris (France).
http://www.logilab.com http://www.logilab.fr http://www.logilab.org
___
Python-Dev mai
On Tuesday 25 April à 01:24, "Martin v. Löwis" wrote:
> Sylvain Thénault wrote:
> > I've posted a patch (#1475523) for this and assigned it to Martin Von
> > Loewis since he was the core developper who has made some followup on
> > the original bug. Could so
