FAQ
Hi Everybody,
I've been doing some test on pythons' virtualenv and recently I've
decided to run PyChecker. But I'm having some difficulties with importing
modules available only on virtualenv by pychecker. As if it was
trying to use systemwide python.
I've googled about it, and found nothing in this area.
I installed pychecker using python setup.py install
from virtualenv. I looked at pychecker script - it uses correct python.

Any help appreciate,
Soltys

Search Discussions

  • Diez B. Roggisch at Feb 3, 2010 at 10:21 pm

    Am 03.02.10 22:46, schrieb soltys:
    Hi Everybody,
    I've been doing some test on pythons' virtualenv and recently I've
    decided to run PyChecker. But I'm having some difficulties with importing
    modules available only on virtualenv by pychecker. As if it was
    trying to use systemwide python.
    I've googled about it, and found nothing in this area.
    I installed pychecker using python setup.py install
    from virtualenv. I looked at pychecker script - it uses correct python.
    I doubt that it uses the "correct python", because then you wouldn't
    have the problems you have.

    I don't use pychecker, but pylint. And there, the system-wide command
    uses the system's python - which of course doesn't know anything about
    virtualenv.

    There are two solutions to this problem:

    - install py(lint|checker) into your virtualenv.
    - write a wrapper-script that invokes py(lint|checker) with an adapted
    PYTHONPATH environtment variable, based on the venv's sys.path. I do
    that for my epylint-wrapper for emacs. Works flawlessly.


    Diez
  • Steve Holden at Feb 4, 2010 at 12:52 am

    Diez B. Roggisch wrote:
    Am 03.02.10 22:46, schrieb soltys:
    Hi Everybody,
    I've been doing some test on pythons' virtualenv and recently I've
    decided to run PyChecker. But I'm having some difficulties with importing
    modules available only on virtualenv by pychecker. As if it was
    trying to use systemwide python.
    I've googled about it, and found nothing in this area.
    I installed pychecker using python setup.py install
    from virtualenv. I looked at pychecker script - it uses correct python.
    I doubt that it uses the "correct python", because then you wouldn't
    have the problems you have.

    I don't use pychecker, but pylint. And there, the system-wide command
    uses the system's python - which of course doesn't know anything about
    virtualenv.

    There are two solutions to this problem:

    - install py(lint|checker) into your virtualenv.
    See the OP's original assertion:
    I installed pychecker using python setup.py install
    from virtualenv. I looked at pychecker script - it uses correct python.
    Isn't that "installing into his virtualenv"?

    regards
    Steve
    - write a wrapper-script that invokes py(lint|checker) with an adapted
    PYTHONPATH environtment variable, based on the venv's sys.path. I do
    that for my epylint-wrapper for emacs. Works flawlessly.


    Diez

    --
    Steve Holden +1 571 484 6266 +1 800 494 3119
    PyCon is coming! Atlanta, Feb 2010 http://us.pycon.org/
    Holden Web LLC http://www.holdenweb.com/
    UPCOMING EVENTS: http://holdenweb.eventbrite.com/
  • Diez B. Roggisch at Feb 4, 2010 at 8:41 am

    Am 04.02.10 01:52, schrieb Steve Holden:
    Diez B. Roggisch wrote:
    Am 03.02.10 22:46, schrieb soltys:
    Hi Everybody,
    I've been doing some test on pythons' virtualenv and recently I've
    decided to run PyChecker. But I'm having some difficulties with importing
    modules available only on virtualenv by pychecker. As if it was
    trying to use systemwide python.
    I've googled about it, and found nothing in this area.
    I installed pychecker using python setup.py install
    from virtualenv. I looked at pychecker script - it uses correct python.
    I doubt that it uses the "correct python", because then you wouldn't
    have the problems you have.

    I don't use pychecker, but pylint. And there, the system-wide command
    uses the system's python - which of course doesn't know anything about
    virtualenv.

    There are two solutions to this problem:

    - install py(lint|checker) into your virtualenv.
    See the OP's original assertion:
    I installed pychecker using python setup.py install
    from virtualenv. I looked at pychecker script - it uses correct python.
    Isn't that "installing into his virtualenv"?
    You are right, it reads like that. I should have read it better.

    All I can say is that even a system-wide pylint with my recipe above
    gives me no troubles.

    Diez

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppython-list @
categoriespython
postedFeb 3, '10 at 9:46p
activeFeb 4, '10 at 8:41a
posts4
users3
websitepython.org

People

Translate

site design / logo © 2022 Grokbase