Best practice for installing python modules from an arbitrary VCS repository

Posted by fmark on Stack Overflow See other posts from Stack Overflow or by fmark
Published on 2010-06-06T23:32:15Z Indexed on 2010/06/06 23:42 UTC
Read the original article Hit count: 430

I'm newish to the python ecosystem, and have a question about module editing.

I use a bunch of third-party modules, distributed on PyPi. Coming from a C and Java background, I love the ease of easy_install <whatever>. This is a new, wonderful world, but the model breaks down when I want to edit the newly installed module for two reasons:

  1. The egg files may be stored in a folder or archive somewhere crazy on the file system.
  2. Using an egg seems to preclude using the version control system of the originating project, just as using a debian package precludes development from an originating VCS repository.

What is the best practice for installing modules from an arbitrary VCS repository? I want to be able to continue to import foomodule in other scripts.

© Stack Overflow or respective owner

Related posts about python

Related posts about best-practices