On 15 Mai, 02:55, [EMAIL PROTECTED] wrote:
> My issues have been with keeping a ~/pylib directory for extra
> modules, and reconciling that with setuptools / Easy Install. I'm
> curious to hear how other folks manage their own local module
> directory.
For Python libraries, I use the workingenv.py
On May 14, 8:55 pm, [EMAIL PROTECTED] wrote:
> On May 14, 6:00 pm, James Stroud <[EMAIL PROTECTED]> wrote:
>
> > [EMAIL PROTECTED] wrote:
> > [snip], but on *nix,
> > you can compile python with the "--prefix=" option set to a directory in
> > your home dir and install there.
>
> Check.
>
> > I rec
On May 14, 6:00 pm, James Stroud <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> [snip], but on *nix,
> you can compile python with the "--prefix=" option set to a directory in
> your home dir and install there.
Check.
> I recommend having your own python install if you want a comprehensi
[EMAIL PROTECTED] wrote:
> What's the customary way to keep your own local Python and package
> directory? For example, when you're on a server where you don't have
> root access, and everything must go in your home directory.
>
> * What directories do you create?
> * What environment variables do
What's the customary way to keep your own local Python and package
directory? For example, when you're on a server where you don't have
root access, and everything must go in your home directory.
* What directories do you create?
* What environment variables do you set?
* What config files do you
