Am 06.03.2010 03:28, schrieb Antoine Pitrou:
> Le Fri, 05 Mar 2010 13:51:15 -0500,
> Neal Becker a écrit :
>> I generally enjoy argparse, but one thing I find rather
>> ugly and unpythonic.
>>
>> parser.add_argument ('--plot', action='store_true')
>
> I would argue that a string is actually
Benjamin Peterson, 06.03.2010 23:13:
A list of changes in 3.1.2rc1 can be found here:
http://svn.python.org/projects/python/tags/r312rc1/Misc/NEWS
Any reason the fix for bug 7173 didn't make it in? The test case that
Amaury came up with seems to indicate that this a pretty serious issue
Brian Curtin wrote:
> On Fri, Mar 5, 2010 at 12:51, Neal Becker wrote:
>
>> I generally enjoy argparse, but one thing I find rather
>> ugly and unpythonic.
>>
>>parser.add_argument ('--plot', action='store_true')
>>
>> Specifying the argument 'action' as a string is IMO ugly.
>>
>
> What el
On Sat, Mar 6, 2010 at 10:09 PM, Dj Gilcrease wrote:
> After playing with the API for a while & running into many issues with
> the examples & tests crashing windows I decided to modify the API a
> little and fix up the examples so they dont crash windows based
> computers.
>
> http://code.google.
Le Sat, 6 Mar 2010 11:43:20 -0800,
Brett Cannon a écrit :
> I see two possible fixes for this. One is to not silence
> DeprecationWarning if Py_DivisionWarningFlag is set to >= 1. The
> other is to introduce a new subclass of DeprecationWarning called
> IntegerDivisionWarning and have that added t
Le Sun, 07 Mar 2010 11:10:52 +0100,
Stefan Behnel a écrit :
>
> Any reason the fix for bug 7173 didn't make it in? The test case that
> Amaury came up with seems to indicate that this a pretty serious
> issue.
The patch needs to properly include an unit test reproducing the test
case.
Also, a c
At 02:49 PM 3/7/2010 +1000, Nick Coghlan wrote:
P.J. Eby wrote:
> (Personally, I think it would be better to just drop the ambitious title
> and scope, and go for the "nice task queue" scope. I imagine, too, that
> in that case Jean-Paul wouldn't need to worry about it being raised as a
> future
On Sun, Mar 7, 2010 at 7:48 AM, P.J. Eby wrote:
> At 02:49 PM 3/7/2010 +1000, Nick Coghlan wrote:
>>
>> P.J. Eby wrote:
>> > (Personally, I think it would be better to just drop the ambitious title
>> > and scope, and go for the "nice task queue" scope. I imagine, too, that
>> > in that case Jean
I download the source snapshot
./configure --enable-framework
make
...
/usr/bin/install -c -d -m 755 Python.framework/Versions/3.1
if test ""; then \
gcc -o Python.framework/Versions/3.1/Python -dynamiclib \
-isysroot "" \
-all_loa
At 08:39 AM 3/7/2010 -0800, Jeffrey Yasskin wrote:
On Sun, Mar 7, 2010 at 7:48 AM, P.J. Eby wrote:
> At 02:49 PM 3/7/2010 +1000, Nick Coghlan wrote:
>>
>> P.J. Eby wrote:
>> > (Personally, I think it would be better to just drop the ambitious title
>> > and scope, and go for the "nice task queue
On Sun, 07 Mar 2010 10:48:09 -0500, "P.J. Eby" wrote:
> At 02:49 PM 3/7/2010 +1000, Nick Coghlan wrote:
> >I agree the PEP should just target what the current implementation
> >provides and put whatever scope limitations are needed in the preamble
> >text to make that clear.
>
> Yep. I'm just sa
On Sun, Mar 7, 2010 at 9:57 AM, P.J. Eby wrote:
> At 08:39 AM 3/7/2010 -0800, Jeffrey Yasskin wrote:
>> Do you have an example of a language or library that uses the term
>> "future" to refer to what you're talking about? I'm curious to see
>> what it looks like.
>
> The wikipedia page menetioned
On Sun, Mar 7, 2010 at 4:29 AM, Neal Becker wrote:
> Brian Curtin wrote:
>
>> On Fri, Mar 5, 2010 at 12:51, Neal Becker wrote:
>>
>>> I generally enjoy argparse, but one thing I find rather
>>> ugly and unpythonic.
>>>
>>> parser.add_argument ('--plot', action='store_true')
>>>
>>> Specifying
At 10:59 AM 3/7/2010 -0800, Jeffrey Yasskin wrote:
So is it that you just don't like the idea of blocking, and want to
stop anything that relies on it from getting into the standard library?
Um, no. As I said before, call it a "parallel task queue" or
"parallel task manager" or something to t
Do you have MacPorts or Fink installed? If you do then you have a version of
gettext installed that is not compiled properly to work with Python (usually
its a 32-bit/64-bit thing). Best piece of advice is to not use MacPorts/Fink
and use Homebrew instead. =)
On Sun, Mar 7, 2010 at 09:36, Brad Mil
We are definitely going to need a 2.6.5 rc 2. We've had a number of critical
issues fixed since rc1 and we have two more critical patches approved for
landing which fix issues on OS X. I've given Ronald approval in the tracker
to land these two patches.
8066 OS X installer: readline module break
On Sun, Mar 7, 2010 at 6:50 AM, Jesse Noller wrote:
> Making the tests and examples happy on windows is fine; but some
> explanation is needed for the API changes.
>
My primary motivation behind the API change is so there is just a
single public Executor class that you tell what system to use ins
On Sun, Mar 7, 2010 at 11:56 AM, P.J. Eby wrote:
> At 10:59 AM 3/7/2010 -0800, Jeffrey Yasskin wrote:
>>
>> So is it that you just don't like the idea of blocking, and want to stop
>> anything that relies on it from getting into the standard library?
>
> Um, no. As I said before, call it a "paral
Hello all,
unittest has seen quite a few new features since Python 2.6. For those
of you who might have missed the announcements in other places,
unittest2 is a backport of the new features in unittest to work with
Python 2.4-2.6. It is already being used for the development of distutils2:
h
Le Mon, 08 Mar 2010 00:51:02 +,
Michael Foord a écrit :
>
> In other news, class and module fixtures (setUpClass /
> tearDownClass / setUpModule / tearDownModule) are now implemented in
> unittest (in trunk
> - not yet merged to py3k). These features are tested but I'm sure
> there are some
On Sun, Mar 7, 2010 at 8:11 PM, Antoine Pitrou wrote:
> Le Mon, 08 Mar 2010 00:51:02 +,
> Michael Foord a écrit :
>>
>> In other news, class and module fixtures (setUpClass /
>> tearDownClass / setUpModule / tearDownModule) are now implemented in
>> unittest (in trunk
>> - not yet merged to
21 matches
Mail list logo
