On Tue, Sep 10, 2013 at 11:16 PM, Ned Deily wrote:
> The behavior is the result of a feature added in 2.7 for Issue4865 which
> appends the site-packages directory for the Apple-supplied system Python
> to sys.path of a Python framework build. With hindsight, I don't think
> this was a good idea
On 11 Sep, 2013, at 8:16, Ned Deily wrote:
> In article
> ,
> Nat Echols wrote:
>> I'm distributing a large cross-platform Python-based application, for which
>> we bundle Python 2.7 and a number of dependencies (wxPython, matplotlib,
>> etc.). We've tried to make it as self-contained as poss
On Tue, Sep 10, 2013 at 11:16 PM, Ned Deily wrote:
> The behavior is the result of a feature added in 2.7 for Issue4865 which
> appends the site-packages directory for the Apple-supplied system Python
> to sys.path of a Python framework build. With hindsight, I don't think
> this was a good idea
In article
,
Nat Echols wrote:
> I'm distributing a large cross-platform Python-based application, for which
> we bundle Python 2.7 and a number of dependencies (wxPython, matplotlib,
> etc.). We've tried to make it as self-contained as possible, to prevent
> either a) polluting the user's envi
I'm distributing a large cross-platform Python-based application, for which
we bundle Python 2.7 and a number of dependencies (wxPython, matplotlib,
etc.). We've tried to make it as self-contained as possible, to prevent
either a) polluting the user's environment and potentially breaking other
pro