* Yaroslav Halchenko , 2010-07-22, 10:54:
It's true that upload of Numpy 1.4 wasn't done with proper care.
However, even if we discovered the breakage earlier, we couldn't
avoid sourceful uploads of the affected packages.
hm... may be we still could...
No. :P
BinNMUs only make sense if there
On Jul 22, 2010, at 10:00 AM, Yaroslav Halchenko wrote:
>
>On Thu, 22 Jul 2010, Barry Warsaw wrote:
>> >But assuming that in longer run we agree on how we invoke
>> >unittesting for Python modules we ship[...]
>
>> I propose this be spelled: 'python setup.py test'.
>
>does setup.py test just do u
On Wed, 21 Jul 2010, Jakub Wilk wrote:
> It's true that upload of Numpy 1.4 wasn't done with proper care.
> However, even if we discovered the breakage earlier, we couldn't
> avoid sourceful uploads of the affected packages.
hm... may be we still could...
> BinNMUs only make sense if there is a v
On Wed, 21 Jul 2010, Sandro Tosi wrote:
> the idea is to restrict versions only on the packages that needs it,
> where the maintaienr will use the --with-pydist=python-foo and have
> the Depends on python-foo generated for him; if it's just an "easy"
> depends on foo, just put python-foo in Depends
On Thu, 22 Jul 2010, Barry Warsaw wrote:
> >But assuming that in longer run we agree on how we invoke unittesting for
> >Python modules we ship[...]
> I propose this be spelled: 'python setup.py test'.
> In my copious spare time , I'm working on code, documentation, and
> infrastructure to make t
On Jul 21, 2010, at 04:17 PM, Yaroslav Halchenko wrote:
>But assuming that in longer run we agree on how we invoke unittesting for
>Python modules we ship[...]
I propose this be spelled: 'python setup.py test'.
In my copious spare time , I'm working on code, documentation, and
infrastructure to
6 matches
Mail list logo
