It's an interesting idea . . . I know why perforce works this way, but I'm curious what problem this addresses. Most of the stuff that lives in the P4CONFIG file is located in <project>/settings.py, as far as I can tell. And I'm not clear how this would solve the problem of Python knowing where to look for your project files in the first place.
- Re: A fix for all that futzing around with paths Tim Keating
- Re: A fix for all that futzing around with paths David Ascher
- Re: A fix for all that futzing around with paths Robert Wittams
- Re: A fix for all that futzing around with p... Simon Willison
- Re: A fix for all that futzing around with paths Adrian Holovaty
- Re: A fix for all that futzing around with p... Sune Kirkeby
- Re: A fix for all that futzing around wi... David Ascher
- Re: A fix for all that futzing arou... Sune Kirkeby
- Re: A fix for all that futzing ... David Ascher
- Re: A fix for all that futz... Simon Willison
- Re: A fix for all that futz... Antonio Cavedoni