Tarek Ziadé wrote:
> Hi,
>
> On behalf of the Distutils-SIG, I would like to propose to addition of
> PEP 345 (once and *if* PEP 386 is accepted).
+1 for integrating all the good work the catalog-sig folks have been doing.
Some comments on PEP 345 specifically though:
The deprecation of the exi
Hi,
On behalf of the Distutils-SIG, I would like to propose to addition of
PEP 345 (once and *if* PEP 386 is accepted).
It's the metadata v1.2: http://www.python.org/dev/peps/pep-0345/
PEP 345 was initiated a while ago by Richard Jones, and reworked since
then together with PEP 386, at Pycon las
Thomas Heller wrote:
> I have to shutdown the x86 osx 5 buildbot slave permanently, because
> the machine is getting a new role. Martin, please remove it from
> the configuration.
Thanks for the notice; I have now removed it from the list.
Regards,
Martin
On Mon, Dec 21, 2009 at 07:02, Mark Dickinson wrote:
> In Python 2.7, PyArg_ParseTuple and friends currently accept a float
> argument where an integer is expected, but produce a
> DeprecationWarning in this case. This can be seen in various places
> in Python proper:
>
> >>> itertools.combinati
In Python 2.7, PyArg_ParseTuple and friends currently accept a float
argument where an integer is expected, but produce a
DeprecationWarning in this case. This can be seen in various places
in Python proper:
>>> itertools.combinations(range(5), 2.0)
__main__:1: DeprecationWarning: integer argumen
On Sun, Dec 20, 2009 at 12:49 AM, "Martin v. Löwis" wrote:
>> Several questions come to mind:
>>
>> 1) Is it reasonable to provide backward compatibility files (either as
>> .h or .c) to provide support to new API calls to extension authors?
>
> I'm skeptical. In my experience, each extension has
I have to shutdown the x86 osx 5 buildbot slave permanently, because
the machine is getting a new role. Martin, please remove it from
the configuration.
--
Thanks,
Thomas
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
