Thanks Chris,
>From earlier in the thread the statement was made:
> i.e would the same binary wheel work for both?
>
> It should, and we will fix issues if they come up.
in reference to Windows builds against MSVC 2008.
I was asking if this "binary compatibility with python.org python" also a
What David said, plus:
On Thu, Jan 9, 2014 at 10:43 PM, Steve Spicklemire wrote:
>
>> So, related question: Should the Mac binaries also work with the
>> python.org mac build?
>
>
Not sure what "also" is respect to, but the pyton.org builds are a good
common denominator:
The Apple builds have th
On Thu, Jan 9, 2014 at 10:43 PM, Steve Spicklemire wrote:
> So, related question: Should the Mac binaries also work with the
> python.org mac build?
>
Binary compatibility is best achieved on windows: the platform makes it
easier, and it is so painful to build stuff there that it would be insane
So, related question: Should the Mac binaries also work with the python.org mac
build?
Regarding my quest: I just punted for now (out of time, need something working
by Monday).
I'm using Christoph Gohlke's binaries for windows (seem to work well!) and
cooked up my own custom installer for Mac
On 9 January 2014 04:44, Chris Barker wrote:
> On Wed, Jan 8, 2014 at 1:48 AM, David Cournapeau wrote:
>>
>> We don't use mingw to build packages distributed within canopy (at least
>> not anymore). We build everything with MSVC 2008, as mixing mingw/MSVC often
>> causes trouble.
>>
>
> so is Can
On Wed, Jan 8, 2014 at 1:48 AM, David Cournapeau wrote:
> We don't use mingw to build packages distributed within canopy (at least
> not anymore). We build everything with MSVC 2008, as mixing mingw/MSVC
> often causes trouble.
>
>
so is Canopy binary-compatible with the python.org builds?
i.e w
This is good news. I'll experiment!
thanks,
-steve
On Jan 8, 2014, at 1:48 PM, David Cournapeau wrote:
>
>
>
> On Wed, Jan 8, 2014 at 6:44 PM, Chris Barker wrote:
> On Wed, Jan 8, 2014 at 1:48 AM, David Cournapeau wrote:
> We don't use mingw to build packages distributed within canopy (at
On Wed, Jan 8, 2014 at 6:44 PM, Chris Barker wrote:
> On Wed, Jan 8, 2014 at 1:48 AM, David Cournapeau wrote:
>
>> We don't use mingw to build packages distributed within canopy (at least
>> not anymore). We build everything with MSVC 2008, as mixing mingw/MSVC
>> often causes trouble.
>>
>>
> so
On Mon, Jan 6, 2014 at 9:55 PM, Chris Barker wrote:
> On Mon, Jan 6, 2014 at 12:26 PM, Steve Spicklemire wrote:
>
>
>> avoid troubling anyone with pesky questions. In that respect I've
>> apparently failed, because here comes the question!
>>
>
> I think this is a use case that is quite useful
On Mon, Jan 6, 2014 at 3:20 PM, Steve Spicklemire wrote:
> Thanks Chris for the detailed reply.
Well, I'm trying to sort out similar issues myself
Right. My impression is/was that python.org/CA/Canopy were all different
> builds of python that were *not* interoperable.
well, in the case
Thanks Chris for the detailed reply.
On Jan 6, 2014, at 4:55 PM, Chris Barker wrote:
> Either/or? As an instructor, I'd recommend you pick one and go with it -- if
> you need wx, that means Canopy for now. Alternatively, you suggest the
> python.org builds, and point your users to binaries the
On Mon, Jan 6, 2014 at 12:26 PM, Steve Spicklemire wrote:
> avoid troubling anyone with pesky questions. In that respect I've
> apparently failed, because here comes the question!
>
I think this is a use case that is quite useful for us all to chew on a
bit...
1st -- yes "Anaconda" refers to
12 matches
Mail list logo
