<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Sun, 9 Sep 2018 at 20:55 Terry Reedy <<a href="mailto:tjreedy@udel.edu">tjreedy@udel.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 9/9/2018 11:39 PM, Jacqueline Kazil wrote:<br>
> Terry -- For clarification, the format question was not a style <br>
> question. It was a reference to the one versus many that I wrote in the <br>
> explainer.<br>
<br>
I don't know what you mean by this.<br>
<br>
> Yes... there are many prescribed formats already. That is the easy part.<br>
<br>
Different publications use different citation formats. We cannot <br>
dictate which format an author or publication uses. We could, and I <br>
think should, suggest the content of the different fields that go into <br>
the various formats. And we could give examples of citing, say, the <br>
Reference Manual, in the most common formats.<br></blockquote><div><br></div><div>What we can suggest, though, is what the information should be and that's what Jackie is initially asking about, i.e. do we want a single reference for the language that is version-agnostic or one for each Python release?</div><div><br></div><div>My vote is a single reference and leave it up to the person referencing to clarify the version they are using. Seems the simplest to maintain long-term.</div><div><br></div><div>-Brett<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
> On Sun, Sep 9, 2018 at 11:33 PM Terry Reedy <<a href="mailto:tjreedy@udel.edu" target="_blank">tjreedy@udel.edu</a> <br>
> <mailto:<a href="mailto:tjreedy@udel.edu" target="_blank">tjreedy@udel.edu</a>>> wrote:<br>
> <br>
> On 9/9/2018 3:43 PM, Jacqueline Kazil wrote:<br>
> > <http:///>The PSF has received a few inquiries asking the question —<br>
> > “How do I cite Python?”So, I am reaching out to you all to figure<br>
> this out.<br>
> ><br>
> > (For those that don’t know my background, I have been in academia<br>
> for a<br>
> > bit as a Ph.D student and have worked at the Library of Congress<br>
> writing<br>
> > code to process Marc records<br>
> <<a href="https://www.loc.gov/marc/bibliographic/" rel="noreferrer" target="_blank">https://www.loc.gov/marc/bibliographic/</a>>,<br>
> > among other things.)<br>
> ><br>
> > IMHO the citation for Python should be decided upon by the Python<br>
> > developers and should live somewhere on the site.<br>
<br>
The PSF is the publisher. It seems that you might be more competent to <br>
make some of the decisions than are we developers, who have mostly left <br>
academia some time ago.<br>
<br>
> > Two questions to be answered…<br>
> ><br>
> > 1. What format should it take?<br>
> <br>
> There are by now formats for citing web documents. I presume style<br>
> guides now include such. Try a current version of the Chicago<br>
> Manual of<br>
> Style. (not sure of exact title). I will ask a university professor<br>
> who should know more than I.<br>
> <br>
> > 2. Where does it live on the site?<br>
> <br>
> On <a href="https://bugs.python.org/issue26597" rel="noreferrer" target="_blank">https://bugs.python.org/issue26597</a>, I suggested the Copyright page.<br>
<br>
To make the answer more visible,<br>
<br>
> I now think a link to 'Citing these Documents' on<br>
> <a href="https://docs.python.org/3/" rel="noreferrer" target="_blank">https://docs.python.org/3/</a><br>
> would be even better.<br>
<br>
tjr<br>
<br>
_______________________________________________<br>
Python-Dev mailing list<br>
<a href="mailto:Python-Dev@python.org" target="_blank">Python-Dev@python.org</a><br>
<a href="https://mail.python.org/mailman/listinfo/python-dev" rel="noreferrer" target="_blank">https://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/brett%40python.org" rel="noreferrer" target="_blank">https://mail.python.org/mailman/options/python-dev/brett%40python.org</a><br>
</blockquote></div></div>