[Python-Dev] Cpython code and ...
I found this:
PyObject *
PyBytes_FromFormat(const char *format, ...)
{
Can someone enlighten me on what the '...' means?
--
~Ethan~
signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Cpython code and ...
It denotes a variadic function:
http://www.gnu.org/software/libc/manual/html_node/Variadic-Functions.html.
On 2015-01-07 11:07 AM, Ethan Furman wrote:
> I found this:
>
> PyObject *
> PyBytes_FromFormat(const char *format, ...)
> {
>
> Can someone enlighten me on what the '...' means?
>
> --
> ~Ethan~
>
>
>
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/demianbrecht%40gmail.com
>
signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Cpython code and ...
On 01/07/2015 11:10 AM, Demian Brecht wrote:
> On 2015-01-07 11:07 AM, Ethan Furman wrote:
>>
>> I found this:
>>
>> PyObject *
>> PyBytes_FromFormat(const char *format, ...)
>> {
>>
>> Can someone enlighten me on what the '...' means?
>
> It denotes a variadic function:
> http://www.gnu.org/software/libc/manual/html_node/Variadic-Functions.html.
Ah, thanks!
--
~Ethan~
signature.asc
Description: OpenPGP digital signature
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] My thinking about the development process
On 6 December 2014 at 06:04, Brett Cannon wrote: > # Next steps > I'm thinking first draft PEPs by February 1 to know who's all-in (8 weeks > away), all details worked out in final PEPs and whatever is required to > prove to me it will work by the PyCon language summit (4 months away). I > make a decision by May 1, and > then implementation aims to be done by the time 3.5.0 is cut so we can > switch over shortly thereafter (9 months away). Sound like a reasonable > timeline? I've now updated PEP 474 to cover my current proposal for the support repositories, as well as some of the preparatory work that is already being undertaken: https://www.python.org/dev/peps/pep-0474/ By the end of the month, I'll also aim to have an updated version of PEP 462 published that considers how the forge.python.org service could potentially be extended to handle CPython itself, rather than attempting to build those flows directly into the existing Roundup and Rietveld based approach. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
