12.09.18 01:23, Victor Stinner пише:
But then Petr Viktorin asked me to open a thread on python-dev to get
a wider discussion. So here I am.
Thank you for opening this discussion Victor. I wanted to do it myself,
but you have wrote much better description of the problem. See also
related
On 2018-09-12 02:00, Ethan Furman wrote:
On 09/11/2018 05:21 PM, Barry Warsaw wrote:
MRAB wrote on 9/11/18 16:06:
Perhaps we could have a single format code plus an optional '#' for
the "alternate form":
%T for short form
%#T for fully qualified name
OTOH, if %T and variants meant "type"
On 09/11/2018 05:21 PM, Barry Warsaw wrote:
MRAB wrote on 9/11/18 16:06:
Perhaps we could have a single format code plus an optional '#' for
the "alternate form":
%T for short form
%#T for fully qualified name
OTOH, if %T and variants meant "type" but %t mean something entirely
On 09/11/18 15:23, Victor Stinner wrote:
Hi,
Last week, I opened an issue to propose to add a new %T formatter to
PyUnicode_FromFormatV() and so indirectly to PyUnicode_FromFormat()
and PyErr_Format():
https://bugs.python.org/issue34595
I merged my change, but then Serhiy Storchaka asked
MRAB wrote on 9/11/18 16:06:
On 2018-09-11 23:23, Victor Stinner wrote:
Last week, I opened an issue to propose to add a new %T formatter to
PyUnicode_FromFormatV() and so indirectly to PyUnicode_FromFormat()
and PyErr_Format():
https://bugs.python.org/issue34595
I merged my change, but
FWIW, I personally think this went to python-dev prematurely. This is a
shallow problem and IMO doesn't need all that much handwringing. Yes, there
are a few different alternatives. So list them all concisely in the tracker
and think about it for a few minutes and then pick one. No matter what's
On 2018-09-11 23:23, Victor Stinner wrote:
Hi,
Last week, I opened an issue to propose to add a new %T formatter to
PyUnicode_FromFormatV() and so indirectly to PyUnicode_FromFormat()
and PyErr_Format():
https://bugs.python.org/issue34595
I merged my change, but then Serhiy Storchaka
On 09/11/18 15:23, Victor Stinner wrote:
Hi,
Last week, I opened an issue to propose to add a new %T formatter to
PyUnicode_FromFormatV() and so indirectly to PyUnicode_FromFormat()
and PyErr_Format():
https://bugs.python.org/issue34595
I merged my change, but then Serhiy Storchaka asked
Hi,
Last week, I opened an issue to propose to add a new %T formatter to
PyUnicode_FromFormatV() and so indirectly to PyUnicode_FromFormat()
and PyErr_Format():
https://bugs.python.org/issue34595
I merged my change, but then Serhiy Storchaka asked if we can add
something to get the "fully
Thanks Wes.
"""
> Python
>
> Guido van Rossum: Scripting the Web with Python. In "Scripting Languages:
> Automating the Web", World Wide Web Journal, Volume 2, Issue 2, Spring
> 1997, O'Reilly.
>
> Aaron Watters, Guido van Rossum, James C. Ahlstrom: Internet Programming
> with Python. MIS
On Tue, Sep 11, 2018 at 2:45 PM, Steven D'Aprano
wrote:
> I think this thread is about *academic* citations.
yes, I assumed that as well, what in any of my posts made you think
otherwise?
> There's a metric ton of information on the web about citing software,
> there are existing standards,
On Sunday, September 9, 2018, Wes Turner wrote:
> "Python Programming Language" (van Rossum, et. Al)
>
> ?
>
> Should there be a URL and/or a DOI?
>
http://www.python.org/~guido/Publications.html
https://gvanrossum.github.io/Publications.html
lists a number of Python citations:
"""
Python
On Tue, Sep 11, 2018 at 11:16:08AM +0200, Chris Barker wrote:
> On Tue, Sep 11, 2018 at 3:48 AM, Steven D'Aprano
> wrote:
>
> > > That is about reproducible results, which is really a different thing
> > than
> > > the usual citations.
> >
> > I don't think it is. I think you are seeing a
On Tue, Sep 11, 2018 at 3:48 AM, Steven D'Aprano
wrote:
> > That is about reproducible results, which is really a different thing
> than
> > the usual citations.
>
> I don't think it is. I think you are seeing a distinction that is not
> there.
no need for us to agree on that, but there are
14 matches
Mail list logo