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 Jan 2014 20:35, "Donald Stufft" wrote:
>
>
> On Jan 9, 2014, at 4:29 AM, Bohuslav Kabrda wrote:
>
> > Hi all,
> > the wheel package format, as defined in pep 427 specifies, that wheel
name can contain an optional "build tag" [1]. This build tag is supposed to
be a tie-breaker if two wheels h
The wheel build tag is only stored in the filename. The feature is not
well tested.
On Thu, Jan 9, 2014 at 7:35 AM, Donald Stufft wrote:
>
> On Jan 9, 2014, at 4:29 AM, Bohuslav Kabrda wrote:
>
>> Hi all,
>> the wheel package format, as defined in pep 427 specifies, that wheel name
>> can conta
On Jan 9, 2014, at 4:29 AM, Bohuslav Kabrda wrote:
> Hi all,
> the wheel package format, as defined in pep 427 specifies, that wheel name
> can contain an optional "build tag" [1]. This build tag is supposed to be a
> tie-breaker if two wheels have the same version. I decided that I would try
Hi all,
the wheel package format, as defined in pep 427 specifies, that wheel name can
contain an optional "build tag" [1]. This build tag is supposed to be a
tie-breaker if two wheels have the same version. I decided that I would try to
send a patch to upstream wheel project [2] to support addi
