On 10 Jul, 2012, at 18:41, Marc Abramowitz wrote:
> Anyone know how to build and run tests on an OS X build with
> —enable-framework, without installing the framework? I want to test
> that something works in my tree without polluting /Library/Frameworks
> with stuff that could mess up future tes
spoke too early on its done sorry
On Tue, Jul 10, 2012 at 2:04 PM, Ryan Paullin wrote:
> thanks for the reply hastings ive been working on a loopback interface its
> done
>
>
> On Fri, Jul 6, 2012 at 3:00 AM, wrote:
>
>> Send Python-Dev mailing list submissions to
>> python-dev@python.o
thanks for the reply hastings ive been working on a loopback interface its
done
On Fri, Jul 6, 2012 at 3:00 AM, wrote:
> Send Python-Dev mailing list submissions to
> python-dev@python.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://mail.python.org/mail
In article ,
Ned Deily wrote:
> Read the updated Mac/README for more information about framework builds.
> Here's a sample configure I use to minimize the chances of pollution
> from other installed Pythons:
>
> BASEDIR="$(dirname $(pwd -P))"
> [ -n "${BASEDIR}" ] && ./configure --enable-uni
In article
,
Marc Abramowitz wrote:
> Anyone know how to build and run tests on an OS X build with
> enable-framework, without installing the framework? I want to test
> that something works in my tree without polluting /Library/Frameworks
> with stuff that could mess up future tests.
>
> I've
Anyone know how to build and run tests on an OS X build with
—enable-framework, without installing the framework? I want to test
that something works in my tree without polluting /Library/Frameworks
with stuff that could mess up future tests.
I've been mucking around with DYLD_FRAMEWORK_PATH but n
