Difference between revisions of "Talk:Python"

From ArchWiki
Jump to: navigation, search
(Remove Section "Misc. Uses")
(Python 2 and 3: re)
 
(12 intermediate revisions by 7 users not shown)
Line 1: Line 1:
== <s> Remove Section "Misc. Uses" </s> ==
+
== Python 2 and 3 ==
  
I would remove the "Misc. Uses" section altogether ("Python is excellent for emergency situations"???) <br />-- [[User:Tokland|Tokland]] 06:12, 25 October 2010 (EDT)
+
[[Python#Python_3]] doesn't mention http://python-future.org/ . It has been recently added to the repos: {{Pkg|python-future}}. I know nothing about python, so I just dropped a note here. -- [[User:Karol|Karol]] ([[User talk:Karol|talk]]) 10:54, 30 August 2015 (UTC)
:I agree that the "Misc. Uses" section doesn't seem appropriate for the ArchWiki. The information in there seems like something I would expect to read on a blog, not on here. If anyone else agrees, I'll remove that section entirely.
+
 
:-- [[User:Jstjohn|Jstjohn]] ([[User talk:Jstjohn|talk]]) 16:36, 27 August 2012 (UTC)
+
:I know python well, but I don't know what's "python-future" xD We can add info about it if another users say it's a good idea -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 13:19, 30 August 2015 (UTC)
:: Done. Close. -- [[User:Fengchao|Fengchao]] ([[User talk:Fengchao|talk]]) 04:05, 8 November 2012 (UTC)
+
 
 +
::[https://docs.python.org/2/library/__future__.html __future__] allows you to use python3 syntax in python2 scripts. Looking at the file list of {{Pkg|python-future}} this is a step up from that. -- [[User:Alad|Alad]] ([[User talk:Alad|talk]]) 19:27, 30 August 2015 (UTC)
 +
 
 +
:::To me it seems like a regular Python package (with rather self-assured name), providing [http://python-future.org/overview.html#automatic-conversion-to-py2-3-compatible-code tools] similar to the older and limited [https://docs.python.org/2/library/2to3.html 2to3] tool. It's not a new [[w:Python_(programming_language)#Implementations|implementation]] or something like that, the ''future'' of Python is to switch to the 3 branch completely. I have no idea why they still (unofficially) backport everything to the 2 branch, thus delaying the inevitable. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 19:59, 30 August 2015 (UTC)
 +
 
 +
:::''"allows you to use python3 syntax in python2 scripts"''
 +
:::So, we can add it in "Dealing with version problem in build scripts" and/or "Tips and tricks" section(s) '''temporarily''', while python2 is widely used -- [[User:Kycok|Kycok]] ([[User talk:Kycok|talk]]) 20:15, 30 August 2015 (UTC)
 +
 
 +
::::That section is targeted at packagers, dealing mainly with the ''python -> python3'' symlink. As far as I understand, the code has to be written explicitly for python-future (or converted automatically and ''checked'') in order to use their features, it can't be used by packagers just for building the packages. -- [[User:Lahwaacz|Lahwaacz]] ([[User talk:Lahwaacz|talk]]) 20:23, 30 August 2015 (UTC)

Latest revision as of 20:24, 30 August 2015

Python 2 and 3

Python#Python_3 doesn't mention http://python-future.org/ . It has been recently added to the repos: python-future. I know nothing about python, so I just dropped a note here. -- Karol (talk) 10:54, 30 August 2015 (UTC)

I know python well, but I don't know what's "python-future" xD We can add info about it if another users say it's a good idea -- Kycok (talk) 13:19, 30 August 2015 (UTC)
__future__ allows you to use python3 syntax in python2 scripts. Looking at the file list of python-future this is a step up from that. -- Alad (talk) 19:27, 30 August 2015 (UTC)
To me it seems like a regular Python package (with rather self-assured name), providing tools similar to the older and limited 2to3 tool. It's not a new implementation or something like that, the future of Python is to switch to the 3 branch completely. I have no idea why they still (unofficially) backport everything to the 2 branch, thus delaying the inevitable. -- Lahwaacz (talk) 19:59, 30 August 2015 (UTC)
"allows you to use python3 syntax in python2 scripts"
So, we can add it in "Dealing with version problem in build scripts" and/or "Tips and tricks" section(s) temporarily, while python2 is widely used -- Kycok (talk) 20:15, 30 August 2015 (UTC)
That section is targeted at packagers, dealing mainly with the python -> python3 symlink. As far as I understand, the code has to be written explicitly for python-future (or converted automatically and checked) in order to use their features, it can't be used by packagers just for building the packages. -- Lahwaacz (talk) 20:23, 30 August 2015 (UTC)