On Mon, Oct 25, 2010 at 01:51:46PM +0200, Arve Knudsen wrote: > Having your package in your project (instead of generating it in the > installation) doesn't prevent PYTHONPATH in any way, it just means you need > another level (i.e., the project) in PYTHONPATH.
Then you need to add every project directory in your python path. This is neither convenient nor the *PATH spirit. The layout of all our project are meant to ease the use of PYTHONPATH setup. Any patch making them "develop" compatible without breaking our main usecase will be welcome. > AFAIK the work is being continued by the "distribute" project. I'm under the > impression at least that the setuptools/distribute way of distributing > Python software is emerging as the standard. To clarify the situation. Distribute is a project that aims replace the setuptools way to install package with a standard way to install package while keeping backward compatibility with setup tools API. In python 3K, distutils2 have been rewritten to include feature included in setuptools and distribute but keep a standard and sane way to install package. > I should definitely like to be able to use "pip" to install e.g. pylint, > especially given the complex dependency set, even if I install some parts of > the chain from Mercurial. Pylint is pip installable. It's just not compatible with the develop command. Setting up a PYTHONPATH is the way to go. regards -- Pierre-Yves David
signature.asc
Description: Digital signature
_______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
