Member Avatar for gunbuster363

python.org tell people to forget about python 2 and head into python 3, but many 3rd party module do not support python 3 at all.
For example, python 3 only ship with a tkinter gui module which does not have great reputation. If I am to use python 3, I have no choice but to use tkinter.

Is python.org want to kill python?

  • 6 Contributors
  • 5 Replies
  • 250 Views
  • 15 Hours Discussion Span
  • Latest Post Latest Post by richieking

Dani AI

Generated

A brief, up-to-date summary and practical next steps (updates the 2010 thread)

In 2010 the hesitation was reasonable — , and others were right to watch third‑party support. The important change since then is that Python 2 has been officially sunset (no more fixes or maintenance as of January 1, 2020), and the core recommendation is to move to Python 3. (python.org)

What that means for GUI toolkits today: tkinter remains the lightweight, built‑in option (it’s in the standard library), but you are not forced to use it. Qt bindings (PyQt and Qt for Python / PySide), wxPython (Phoenix), and GTK via PyGObject all have maintained Python‑3 support and published install paths/wheels; most projects now distribute wheels on PyPI or clearly documented installers. Try the toolkit you prefer and test it in an isolated environment rather than assuming tkinter is the only choice. (docs.python.org)

Practical, low‑risk workflow for trying or migrating:

  • Keep both interpreters while you evaluate, but start new code on Python 3.
  • Use a virtual environment and pip to test GUI bindings in isolation.
  • For porting, prefer maintained helpers (futurize / python‑modernize / python‑future) and follow the official porting HOWTO; note that the stdlib 2to3 tool is now deprecated and third‑party tools are recommended for complex projects. Example quick test:
python3 -m venv .venv
source .venv/bin/activate   # Windows: .venv\Scripts\activate
python -m pip install --upgrade pip
python -m pip install pyside6   # or pyqt6, wxpython, pygobject
python -c "import PySide6, wx, gi, tkinter"

See the venv/pip guidance and porting HOWTO for exact steps and edge cases. The short takeaway: for new work, choose Python 3 and the GUI toolkit that fits your needs; for legacy code, port gradually in virtualenvs and test each dependency before committing. (docs.python.org)

Recommended Answers

All 5 Replies

Member Avatar for Gribouillis

I suggest that you start contributing to the porting of other gui toolkits to python 3 !

Member Avatar for convoluted

wxWidgets does not support Python 3 (yet), so for me it's a deal breaker. I'm quite happy with Python 2.6, no need to switch to 3 at the moment.

Member Avatar for snippsat

python.org tell people to forget about python 2 and head into python 3.

No they do not.

For example, python 3 only ship with a tkinter gui module which does not have great reputation. If I am to use python 3, I have no choice but to use tkinter.

No,you have not PyQT and PyGTK has been portet to python 3,so plase uppdate yourself.
We had many thread about python 2 or 3 her on daniweb
To make it simple python is python,have both installed and learn what the diffrence are.
Then there is no problem to switch back and fourth.
One therad that was about this recently.
http://www.daniweb.com/forums/thread324004.html

Member Avatar for richieking

Why upgrade if 2x does the job fine.

good things come to those who wait. ;)

Edited by richieking because: n/a
Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.