* Mike Hommey , 2010-11-18, 12:17:
A number of packages in the archive sets the PYTHONPATH environment
variable in an insecure way. They do something like:
PYTHONPATH=/spam/eggs:$PYTHONPATH
This is wrong, because if PYTHONPATH were originally unset or empty,
current working directory wou
On Thu, Nov 18, 2010 at 07:04:07PM +0800, Paul Wise wrote:
> > On Wed, Nov 17, 2010 at 22:58, Jakub Wilk wrote:
> >> A number of packages in the archive sets the PYTHONPATH environment
> >> variable
> >> in an insecure way. They do something like:
> >>
> >> PYTHONPATH=/spam/eggs:$PYTHONPATH
> On Wed, Nov 17, 2010 at 22:58, Jakub Wilk wrote:
>> A number of packages in the archive sets the PYTHONPATH environment variable
>> in an insecure way. They do something like:
>>
>> PYTHONPATH=/spam/eggs:$PYTHONPATH
>>
>> This is wrong, because if PYTHONPATH were originally unset or empty,
Hi all,
here below the mail Jakub sent to d-python yesterday, I'm bouncing it
now to d-d now to wider spread and as a notification of an upcoming
mbf (if no stop comes it's expected to happen this evening). Please
follow the whole thread at [1] for further discussion (and keep d-p in
the loop in ca
4 matches
Mail list logo
