Talk:CPython

  Y Merger complete.

CPython supported platforms?

I overhauled previously bogus "CPython supported platforms" section, separating to "supported", "previously supported", and "external". I also linked to the development sites where external ports are actually developed. Sanxiyn 08:10, 14 August 2007 (UTC)

"Classic Python"

http://www.google.co.uk/search?hl=en&safe=off&q=%22classic+python%22+cpython+-gfdl+-wikipedia&btnG=Search&meta= hints at this term actually having some currency. Draw your own conclusion. 88.111.156.134 17:32, 15 April 2007 (UTC)

Image copyright problem with Image:Python logo.svg

The image Image:Python logo.svg is used in this article under a claim of fair use, but it does not have an adequate explanation for why it meets the requirements for such images when used here. In particular, for each page the image is used on, it must have an explanation linking to that page which explains why it needs to be used on that page. Please check

• That there is a non-free use rationale on the image's description page for the use in this article.
• That this article is linked to from the image description page.

This is an automated notice by FairuseBot. For assistance on the image use policy, see Wikipedia:Media copyright questions. --01:11, 2 October 2008 (UTC)

The supported platforms part of this article is really dumb. Why are OS's separated as "unix like" and "desktop"? Linux and OS X are both Unix-like desktop OS's. —Preceding unsigned comment added by 209.89.155.169 (talk) 21:00, 12 May 2010 (UTC)

Citation Needed tags in a weird place

In the "Supported Platforms" section, there are "Citation needed" tags on the headers for the "Other" and "Special Embedded" sections. This positioning makes no sense; the source to cite for these platforms being supported is not necessarily going to cover all of them. They would be better on the contested supported platforms. 141.217.174.122 (talk) 18:28, 16 November 2012 (UTC)

z/OS a supported platform?

To claim z/OS is a supported platform might be pushing it a bit. See http://bugs.python.org/issue1298 . — Preceding unsigned comment added by 194.137.52.222 (talk) 12:29, 2 April 2014 (UTC)

Unladen swallow

CPython#Unladen Swallow is too long. Since it is clear that development on Unladen swallow is not continuing, the detective work to try to see if anything has been happening since 2010 is no longer of much interest. In my opinion this section might be shortened into a summary. EdJohnston (talk) 22:11, 3 August 2018 (UTC)

Not only is it too long, it should not be in CPython at all as it is NOT CPython. On the other hand there is no specific page for it, and it seems a shame to 'destroy' information even if it does refer to a project that is only of historic interest. Perhaps there should be a Wikipedia page specifically for summarising Python implementations? — Preceding unsigned comment added by 80.94.115.69 (talk) 09:49, 6 March 2019 (UTC)

It used to have its own page, see Talk:Unladen Swallow, but was uncontroversially moved here. Pianostar9 (talk) 13:47, 9 August 2019 (UTC)

Maybe move it to History of Python? Tgpqaz (talk) 22:57, 12 November 2021 (UTC)

GIL "rewrite"

The recent commit "Rewrote the explanation of the GIL to make it's Pros, Cons and characteristics clearer." is long on opinions and short on citations. — Preceding unsigned comment added by DoctorCaligari (talk • contribs) 17:01, 21 March 2019 (UTC)

I agree, should we remove it? LetterC (talk) 17:27, 18 August 2020 (UTC)

"Python [...] is generally not used for CPU-intensive operations such as image-processing or neural networks"

Python and machine learning go hand-in-hand, Python is used all the time for neural networks. Should this be changed? Chameleon world

If you remove most of that section, I don't think anyone is going to stop you Akeosnhaoe (talk) 04:44, 8 January 2020 (UTC)

"Python is typically used at the top level and calls functions in libraries to perform specialized tasks. These libraries are generally not written in Python and Python code in another thread can be executed while a call to one of these underlying processes takes place. The non-Python library being called to perform the CPU-intensive task is not subject to the GIL and may concurrently execute many threads on multiple processors without restriction." Doesn't this clarify the issue, OP? Python is used for IP and NN, but this doesn't mean that all the ML libraries are written in Python all the way down. pytorch has more C++ than Python checked in, for instance. BernardoSulzbach (talk) 19:11, 8 January 2020 (UTC)

That makes sense, thank you. I removed it anyways as the phrasing is ambiguous and slightly confusing to me and possibly others. I don't believe the article loses any important information without it. Chameleon world

I think your edit is net positive. If you are not used to it, start signing your comments with (~~~~) so it is easier to see who said what. BernardoSulzbach (talk) 19:27, 8 January 2020 (UTC)