I wanted to send an update.
At the NumFocus Summit, I found out about...
This: https://www.force11.org/group/software-citation-working-group
& this: https://github.com/adrn/CitationPEP
I am going to work on a citation approach based off of those two sources
and come back with a more developed prop
On 2018-09-17 05:05, Jeremy Hylton wrote:
I wanted to start with an easy answer that is surely unsatisfying:
http://blog.apastyle.org/apastyle/2015/01/how-to-cite-software-in-apa-style.html
APA style is pretty popular, and it says that standard software doesn't
need to be specified. Standard s
Jacqueline Kazil writes:
> I thought I could take two to three concrete formats and user test
> there and report on how community members who would be using the
> citation feel.
+1
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.pytho
Foundation, https://docs.python.org/reference/index.html. Retrieved 16
September 2018.
I'd say that's all settled. If anyone asks you, "How can you be sure that
settles it?" You can answer, "Some guy said it on a mailing list." And then
you can site the message:
Jere
I think the "why" in this case should be a bit deeper than that, because
until recently, it's been somewhat unusual to cite the /tools you use/
to create a paper.
I see three major reasons why people cite software packages, and the
form of the citation would have different requirements for each on
Cool, thanks!
On Sun, Sep 16, 2018 at 7:19 PM Brett Cannon wrote:
>
>
> On Sun, 16 Sep 2018 at 15:23 Jacqueline Kazil
> wrote:
>
>> RE: Why cite Python….
>>
>> I would say that in this paper —
>> http://conference.scipy.org/proceedings/scipy2015/pdfs/jacqueline_kazil.pdf,
>> where we introduced
On Sun, 16 Sep 2018 at 15:23 Jacqueline Kazil wrote:
> RE: Why cite Python….
>
> I would say that in this paper —
> http://conference.scipy.org/proceedings/scipy2015/pdfs/jacqueline_kazil.pdf,
> where we introduced a new library, we should have cited Python, because the
> library was based in Pyt
RE: Why cite Python….
I would say that in this paper —
http://conference.scipy.org/proceedings/scipy2015/pdfs/jacqueline_kazil.pdf,
where we introduced a new library, we should have cited Python, because the
library was based in Python. We were riding on the coattails of Python and
if Python did n
Jacqueline Kazil writes:
> *As a user, I am writing an academic paper and I need to cite Python. *
I don't understand the meaning of "need" and "Python". To understand
your code, one likely needs the Language Reference and surely the
Library Reference, and probably documentation of the APIs and
On Sun, Sep 09, 2018 at 03:43:13PM -0400, Jacqueline Kazil wrote:
> The PSF has received a few inquiries asking the question — “How do I cite
> Python?”So, I am reaching out to you all to figure this out.
What about the R approach?
---
> citation()
To cite R in publications use:
R Core Team (
>
> On Saturday, September 15, 2018, Jacqueline Kazil
> wrote:
>
>> I just got caught up on the thread. This is a really great discussion.
>> Thank you for all the contributions.
>>
>> Before we get into the details, let's go back to the main use case we are
>> trying to solve.
>> *As a user, I am
On Saturday, September 15, 2018, Jacqueline Kazil
wrote:
> I just got caught up on the thread. This is a really great discussion.
> Thank you for all the contributions.
>
> Before we get into the details, let's go back to the main use case we are
> trying to solve.
> *As a user, I am writing an a
I just got caught up on the thread. This is a really great discussion.
Thank you for all the contributions.
Before we get into the details, let's go back to the main use case we are
trying to solve.
*As a user, I am writing an academic paper and I need to cite Python. *
Let's throw reproducibilit
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, yo
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
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", defini
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
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 Press/He
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, a
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 distinc
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 sti
I also see reproducibility and citation graphs as distinct concepts.
If it's reproducibility you're after, bibliographic citations are very
unlikely to enable someone else to assemble an identical build environment
from which the same conclusion should be repeatably derivable.
A ScholarlyArticle
On Mon, Sep 10, 2018 at 09:25:29PM +0200, Chris Barker via Python-Dev wrote:
> I"d like ot know what thee citations are expected to be used for?
>
> i.e. -- usually, academic papers have a collection of citiations to
> acknowledge where you got an idea, or fact, or It serves both to
> jusstif
I"d like ot know what thee citations are expected to be used for?
i.e. -- usually, academic papers have a collection of citiations to
acknowledge where you got an idea, or fact, or It serves both to
jusstify something and make it clear that it is not your own idea (i.e. not
pagerism).
in the
On Sun, 9 Sep 2018 at 20:55 Terry Reedy wrote:
> On 9/9/2018 11:39 PM, Jacqueline Kazil wrote:
> > Terry -- For clarification, the format question was not a style
> > question. It was a reference to the one versus many that I wrote in the
> > explainer.
>
> I don't know what you mean by this.
>
>
Wouldn't it make sense to ask the developers of the other Python
implementations too?
Just my 0.02€,
Gerald
Am 09.09.2018 um 21:43 schrieb Jacqueline Kazil:
The PSF has received a few inquiries asking the question — “How do I cite
Python?”So, I am reaching out to you all to figure this out
On 9/9/2018 11:39 PM, Jacqueline Kazil wrote:
Terry -- For clarification, the format question was not a style
question. It was a reference to the one versus many that I wrote in the
explainer.
I don't know what you mean by this.
Yes... there are many prescribed formats already. That is the e
Terry -- For clarification, the format question was not a style question.
It was a reference to the one versus many that I wrote in the explainer.
Yes... there are many prescribed formats already. That is the easy part.
-Jackie
On Sun, Sep 9, 2018 at 11:33 PM Terry Reedy wrote:
> On 9/9/2018 3:
On 9/9/2018 3:43 PM, Jacqueline Kazil wrote:
The PSF has received a few inquiries asking the question —
“How do I cite Python?”So, I am reaching out to you all to figure this out.
(For those that don’t know my background, I have been in academia for a
bit as a Ph.D student and have worked at t
"Python Programming Language" (van Rossum, et. Al)
?
Should there be a URL and/or a DOI?
Figshare and Zenodo will archive a [e.g. tagged] [GitHub] revision and
generate a DOI, AFAIU
On Sunday, September 9, 2018, Steven D'Aprano wrote:
> On Sun, Sep 09, 2018 at 03:43:13PM -0400, Jacqueli
On Sun, Sep 09, 2018 at 03:43:13PM -0400, Jacqueline Kazil wrote:
> The PSF has received a few inquiries asking the question — “How do I cite
> Python?”So, I am reaching out to you all to figure this out.
If you figure it out, it would be lovely to see some movement on this
ticket:
https://bugs.
On Sun, Sep 9, 2018, 14:19 Jacqueline Kazil wrote:
> The PSF has received a few inquiries asking the question — “How do I cite
> Python?”So, I am reaching out to you all to figure this out.
>
> (For those that don’t know my background, I have been in academia for a
> bit as a Ph.D student and hav
The PSF has received a few inquiries asking the question — “How do I cite
Python?”So, I am reaching out to you all to figure this out.
(For those that don’t know my background, I have been in academia for a bit
as a Ph.D student and have worked at the Library of Congress writing code
to process Ma
34 matches
Mail list logo
