-- http://www.ironpythoninaction.com On 19 Feb 2010, at 22:52, Eric Smith <eric at trueblade.com> wrote: > Glenn Linderman wrote: >> On approximately 2/19/2010 1:18 PM, came the following characters >> from the keyboard of P.J. Eby: >>> At 01:49 PM 2/19/2010 -0500, Ian Bicking wrote: >>>> I'm not sure how this should best work on Windows (without >>>> symlinks, >>>> and where things generally work differently), but I would hope if >>>> this idea is more visible that someone more opinionated than I >>>> would >>>> propose the appropriate analog on Windows. >>> >>> You'd probably have to just copy pythonv.exe to an appropriate >>> directory, and have it use the configuration file to find the "real" >>> prefix. At least, that'd be a relatively obvious way to do it, >>> and it >>> would have the advantage of being symmetrical across platforms: just >>> copy or symlink pythonv, and make sure the real prefix is in your >>> config file. >>> >>> (Windows does have "shortcuts" but I don't think that there's any >>> way >>> for a linked program to know *which* shortcut it was launched from.) >> No automatic way, but shortcuts can include parameters, not just >> the program name. So a parameter could be --prefix as was >> suggested in another response, but for a different reason. > > Shortcuts don't work from the shell (well, cmd.exe, at least), do > they? Can't test from here. They do if you add .lnk to your PATHEXT environment variable. Michael > > _______________________________________________ > Python-Dev mailing list > Python-Dev at python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: http://mail.python.org/mailman/options/python-dev/fuzzyman%40voidspace.org.uk
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4