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 software includes "Microsoft Word, Java, and
Ad
Are all current Python builds and C extensions vulnerable to Spectre
variants {1, 2, *}?
There are now multiple threads:
"SEC: Spectre variant 2: GCC: -mindirect-branch=thunk
-mindirect-branch-register"
-
https://mail.python.org/mm3/archives/list/distutils-...@python.org/thread/4BGE226DB5EWIAT5VC
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
On Fri, 14 Sep 2018 14:27:37 -0700
Larry Hastings wrote:
>
> I don't propose to merge the patch in its current state. I think it
> would need a lot of work both in terms of "doing things the way Python
> does it" as well as just code smell (the serializer is implemented in
> both C and Python
On 2018-09-15, Paul Moore wrote:
> On Fri, 14 Sep 2018 at 23:28, Neil Schemenauer wrote:
> > We could have a new format, .pya (compiled python archive) that has
> > data for many .pyc files in it.
[..]
> Isn't that essentially what putting the stdlib in a zipfile does? (See
> the windows embedded
On Sunday, September 16, 2018, Wes Turner wrote:
> Should Python builds add `-mindirect-branch=thunk
> -mindirect-branch-register` to CFLAGS?
>
> Where would this be to be added in the build scripts with which
> architectures?
>
> /QSpectre is the MSVC build flag for Spectre Variant 1:
>
> > The
Should Python builds add `-mindirect-branch=thunk
-mindirect-branch-register` to CFLAGS?
Where would this be to be added in the build scripts with which
architectures?
/QSpectre is the MSVC build flag for Spectre Variant 1:
> The /Qspectre option is available in Visual Studio 2017 version 15.7 a
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
11 matches
Mail list logo
