Most recent 15 issues waiting for review (15)
=
Just curious: How is a issue considered "waiting for review"?
Thanks!
francis
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python
Zitat von francis :
Most recent 15 issues waiting for review (15)
=
Just curious: How is a issue considered "waiting for review"?
Issues that have the "patch" or "needs review" keyword or are
in the "patch review" stage.
Regards,
Martin
Most recent 15 issues waiting for review (15)
=
Just curious: How is a issue considered "waiting for review"?
Issues that have the "patch" or "needs review" keyword or are
in the "patch review" stage.
Thank you!
Is there a easy way to aut
Zitat von francis :
Is there a easy way to automate this?:
- Get a list the "waiting for review" issues
Not exactly this precise list; instead, a list of issues with a patch:
s=xmlrpclib.ServerProxy("http://bugs.python.org",allow_none=True)
s.filter('issue',dict(keywords=2,status=1})
The o
Hi,
On Sat, Aug 25, 2012 at 2:07 PM, wrote:
>
> Zitat von francis :
>
>
>> Is there a easy way to automate this?:
>>
>> - Get a list the "waiting for review" issues
>
>
> Not exactly this precise list; instead, a list of issues with a patch:
>
> s=xmlrpclib.ServerProxy("http://bugs.python.org",a
> Compatibility issues may lead to other strange bugs, too. IIRC each
> msvcrt has its own thread local storage and therefore its own errno
> handling. An extension compiled with VS 2010 won't be able to use the
> PyErr_SetFromErrno*() function correctly. That's much harder to debug
> than a FILE p
"Martin v. L?wis" wrote:
> - each CRT has its own locale. This may be an issue if an extension
> module relies on the CRT locale for data formatting; I just think
> this is unlikely to occur in practice (and when it does, it's easily
> notable).
_decimal's 'n' format specifier actually reli
On 25.08.2012 19:36, Stefan Krah wrote:
> "Martin v. L?wis" wrote:
>> - each CRT has its own locale. This may be an issue if an extension
>> module relies on the CRT locale for data formatting; I just think
>> this is unlikely to occur in practice (and when it does, it's easily
>> notable).
On behalf of the Python development team, I'm delighted to announce the
first release candidate of Python 3.3.0.
This is a preview release, and its use is not recommended in
production settings.
Python 3.3 includes a range of improvements of the 3.x series, as well
as easier porting between 2.x
