Christopher Barker wrote:
> David Cournapeau wrote:
>> On Thu, Jan 7, 2010 at 1:35 AM, Christopher Barker
>>> In the past, I think folks' have used the default
>>> name provided by bdist_mpkg, and those are not always clear. Something like:
>>>
>>>
>>> numpy1.4-osx10.4-python.org2.6-32bit.dmg
>> Th
On Wed, Jan 6, 2010 at 11:35 AM, Christopher Barker
wrote:
>
> It's worse to have a binary you expect to work fail for you than to not
> have one available. IN the past, I think folks' have used the default
> name provided by bdist_mpkg, and those are not always clear. Something like:
>
>
> numpy1
David Cournapeau wrote:
> On Thu, Jan 7, 2010 at 1:35 AM, Christopher Barker
>> In the past, I think folks' have used the default
>> name provided by bdist_mpkg, and those are not always clear. Something like:
>>
>>
>> numpy1.4-osx10.4-python.org2.6-32bit.dmg
>
> The 32 bits is redundant - we supp
On Thu, Jan 7, 2010 at 1:35 AM, Christopher Barker
wrote:
> One more note:
>
> An easy improvement to the current situation with binaries is to LABEL
> THEM WELL:
>
> It's worse to have a binary you expect to work fail for you than to not
> have one available. IN the past, I think folks' have used
One more note:
An easy improvement to the current situation with binaries is to LABEL
THEM WELL:
It's worse to have a binary you expect to work fail for you than to not
have one available. IN the past, I think folks' have used the default
name provided by bdist_mpkg, and those are not always c
