Currently, the README describes a few different ways to set up a project environment using cp4pc, none of which are particularly appetizing in general. The provide methods are as follows:
- Place cp4pc in a directory and mutate one's global PYTHONPATH
- On a project by project basis, find a way to incorporate cp4pc and mutate sys.path
Essentially, both these methods are fragile and do not take advantage of the facilities for package management that are an integral part of the python ecosystem. Adding a properly written setup.py and adjusting some things will greatly enhance the usability of those who are wise enough to take advantage of systems like virtualenv or buildout.
Currently, the README describes a few different ways to set up a project environment using cp4pc, none of which are particularly appetizing in general. The provide methods are as follows:
Essentially, both these methods are fragile and do not take advantage of the facilities for package management that are an integral part of the python ecosystem. Adding a properly written setup.py and adjusting some things will greatly enhance the usability of those who are wise enough to take advantage of systems like virtualenv or buildout.