Talk:CPython

message: 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)
thread_title:  CPython supported platforms? 

message: 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)
thread_title:  "Classic Python" 

message: 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)
thread_title: Image copyright problem with Image:Python logo.svg

message: 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)
thread_title:  Citation Needed tags in a weird place 

message: 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)
thread_title:  z/OS a supported platform? 

message: 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)
replies: text: 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)
replies: text: It used to have its own page, see Talk:Unladen Swallow, but was uncontroversially moved here. Pianostar9 (talk) 13:47, 9 August 2019 (UTC)
replies: text: Maybe move it to History of Python? Tgpqaz (talk) 22:57, 12 November 2021 (UTC)
thread_title:  Unladen swallow 

message: 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)
replies: text: I agree, should we remove it? LetterC (talk) 17:27, 18 August 2020 (UTC)
thread_title:  GIL "rewrite"