symlink optional (feature)

Bug #442780 reported by Roland Schulz
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Virtualenv
New
Undecided
Unassigned

Bug Description

It would be nice to have an option -copy or -nosymlink to force coping instead of symlinking. It can be very easily be done by just:
delattr(os,"symlink")

Revision history for this message
Ian Bicking (ianb) wrote : Re: [Bug 442780] [NEW] symlink optional (feature)

Out of curiosity, what do you want this feature for?

Revision history for this message
Roland Schulz (roland-rschulz) wrote :

I wanted to create a virtual env in a network mounted directory. Thus
symlinks don't work because they point to the file on the computer where one
creates the virtual env which are not necessary available on other
machines/nodes.

On Fri, Oct 16, 2009 at 6:30 PM, Ian Bicking
<<email address hidden><ianbicking%<email address hidden>>
> wrote:

> Out of curiosity, what do you want this feature for?
>
> --
> symlink optional (feature)
> https://bugs.launchpad.net/bugs/442780
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Virtualenv: library isolated for Python: New
>
> Bug description:
> It would be nice to have an option -copy or -nosymlink to force coping
> instead of symlinking. It can be very easily be done by just:
> delattr(os,"symlink")
>

--
ORNL/UT Center for Molecular Biophysics cmb.ornl.gov
865-241-1537, ORNL PO BOX 2008 MS6309

Revision history for this message
tenfishsticks (tenfishsticks) wrote :

I have the same issue, I need to create python environments to push out to a cluster.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.