There was a thread about adding __cite__ to things and a tool to collect
those citations awhile back.
"[Python-ideas] Add a __cite__ method for scientific packages"
http://markmail.org/thread/rekmbmh64qxwcind
Which CPython source file should contain this __cite__ value?
... On a related note,
Do you guys think we should all cite Grub and BusyBox and bash and libc and
setuptools and pip and openssl and GNU/Linux and LXC and Docker; or else
it's plagiarism for us all?
#OpenAccess
On Wednesday, September 12, 2018, Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> wrote:
>
Chris Barker via Python-Dev writes:
> But "I wrote some code in Python to produce these statistics" --
> does that need a citation?
That depends on what you mean by "statistics" and whether (as one
should) one makes the code available. If the code is published or
"available on request",
Hi,
For the type name, sometimes, we only get a type (not an instance),
and we want to format its FQN. IMHO we need to provide ways to format
the FQN of a type for *types* and for *instances*. Here is my
proposal:
* Add !t conversion to format string
* Add ":T" format to type.__format__()
* Add
On 06/20/18 01:53, Jeroen Demeyer wrote:
Hello,
Let me present PEP 579 and PEP 580.
PEP 579 is an informational meta-PEP, listing some of the issues with
functions/methods implemented in C. The idea is to create several PEPs
each fix some part of the issues mentioned in PEP 579.
PEP 580 is
Oh yes, one issue of missing bpo-xxx is that bots don't report merged
commits into the bpo. I like using the bpo issue to track backports:
https://bugs.python.org/issue31902
It was just a general remark, it's fine for these commits. Someone can
add them manually to the bpo if you want.
Victor
Hi Benjamin,
https://github.com/python/cpython/commit/d13e59c1b512069d90efe7ee9b613d3913e79c56
Le mer. 12 sept. 2018 à 17:19, Benjamin Peterson a écrit :
> (Just checking) Is there something wrong with this message besides the <--
> comment?
Since the commit is described as a follow-up of
On Wed, Sep 12, 2018, at 01:33, Serhiy Storchaka wrote:
> 12.09.18 01:34, Miss Islington (bot) пише:
> > https://github.com/python/cpython/commit/d13e59c1b512069d90efe7ee9b613d3913e79c56
> > commit: d13e59c1b512069d90efe7ee9b613d3913e79c56
> > branch: master
> > author: Benjamin Peterson
> >
Thanks Zach for fixing it quickly.
Even if that bug has been fixed, per my instructions to python-committers,
core devs should still edit the PR title and PR description *before* adding
the '烙 automerge' label.
The YouTube video (link in python-committers email) shows to edit those.
The PR
It is still up to the core dev to set the message properly, but the HTML
comments are invisible on GitHub until you edit the message. That bug is
now fixed, though; HTML comments are stripped from the message before
creating the commit.
--
Zach
(Top-posted in HTML from a phone)
On Wed, Sep 12,
12.09.18 01:34, Miss Islington (bot) пише:
https://github.com/python/cpython/commit/d13e59c1b512069d90efe7ee9b613d3913e79c56
commit: d13e59c1b512069d90efe7ee9b613d3913e79c56
branch: master
author: Benjamin Peterson
committer: Miss Islington (bot)
On Tue, Sep 11, 2018 at 10:35:04PM +0200, Chris Barker wrote:
> 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?
When you started talking about
12 matches
Mail list logo
