* Jakub Wilk , 2010-07-28, 18:35:
looking at sip4-qt3 build log, even the PPA version provides only
modules for 2.6, which looks like a bug in sip4-qt3.
Actually, it's python-defaults in toolchain2.7 PPA, which does not
support python2.7. Yay.
--
Jakub Wilk
signature.asc
Description: Digit
On Jul 27, 2010, at 09:48 PM, Yaroslav Halchenko wrote:
>well, both "setup.py test" and "module.test()" sound like reasonable
>interfaces to adhere to.
Yes, especially if 'python -m module.test' were an available command line
interface. The former could be promoted for in-development testing and
On Jul 27, 2010, at 05:56 PM, Yaroslav Halchenko wrote:
>On Thu, 22 Jul 2010, Barry Warsaw wrote:
>> In my copious spare time , I'm working on code, documentation,
>> and infrastructure to make this the preferred way of testing Python
>> modules and applications. You don't *have* to conform, but
On Jul 28, 2010, at 12:23 AM, Sandro Tosi wrote:
>anyhow, since I'm at it: please don't force ANY testing tool; I kinda
>like unittest2, and it's available in python2.7 stdlib, and it's also
>backported to 2.4-2.6 (and even packaged for debian), and I don't want
>to be forced to use nose for my up
On Jul 29, 2010, at 03:35 PM, Jakub Wilk wrote:
>* Jakub Wilk , 2010-07-28, 18:35:
>>looking at sip4-qt3 build log, even the PPA version provides only
>>>modules for 2.6, which looks like a bug in sip4-qt3.
>
>Actually, it's python-defaults in toolchain2.7 PPA, which does not
>support python2.7. Y
On Tue, Jul 27, 2010 at 11:41:19AM +0200, Emilio Pozuelo Monfort wrote:
> On 27/07/10 08:54, Sandro Tosi wrote:
> > On Tue, Jul 27, 2010 at 08:48, Josselin Mouette wrote:
> >> Le mardi 27 juillet 2010 à 10:33 +0900, Shyouzou Sugitani a écrit :
> >>> After upgrading from 2.17.0-2 to 2.17.0-3 I got
6 matches
Mail list logo
