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 enclosed doc, it says: """ *If someone publishes research, they will cite the exact major version that was used, so if someone was trying to recreate the research they would be able to do it.* *"""* That is about reproducible results, which is really a different thing than the usual citations. In that case, you would want some way to identify the actual source code (cPython version 3.6.4, and probably a url to the source -- but how long might that last???) And you would need to post your own source anyway. Again, regular citation is about acknowledging the source of an idea or fact, or something of that nature. I can imagine a paper about computer language design or some such might need to reference Python -- in which case it should reference the Language Reference, I suppose. Maybe we should have a DOI for each version of the standard docs. But "I wrote some code in Python to produce these statistics" -- does that need a citation? If so, maybe that would take a different form. Anyway, hard to make this decision without some idea how the citation is intended to be used. -CHB On Mon, Sep 10, 2018 at 9:51 AM, Gerald Klix <python...@klix.ch> wrote: > 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. >> >> (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 Marc records <https://www.loc.gov/marc/bibliographic/>, among >> other things.) >> >> IMHO the citation for Python should be decided upon by the Python >> developers and should live somewhere on the site. >> >> Two questions to be answered… >> >> 1. What format should it take? >> 2. Where does it live on the site? >> >> To help frame the first one, I quickly wrote this up — >> https://docs.google.com/document/d/1R0mo8EYVIPNkmNBImpcZTbk0 >> e78T2oU71ioX5NvVTvY/edit# >> >> tldr; Summary of possibilities… >> >> 1. Article for one citation (1 DOI, generated by the publication) >> 2. No article (many DOIs — one for each major version through Zenodo >> <https://zenodo.org/record/1404209> (or similar service)) >> >> Discuss. >> >> -Jackie >> >> Jackie Kazil >> Board of Directors, PSF >> >> >> >> _______________________________________________ >> 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/python. >> 00%40klix.ch >> > > _______________________________________________ > 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/chris. > barker%40noaa.gov > -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov
_______________________________________________ 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