Variety

Port to Python 3

Bug #1337320 reported by Peter Levi
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Variety
Fix Released
Medium
Unassigned

Bug Description

Check if it's worth porting to Python 3 and if all the libraries we use are available.

For now there is one known issue that will be resolved by this - power usage is higher than it should be because of the polling in threading.Event.wait() in Python 2.7 which causes at least 20 interruptions per second.

Revision history for this message
Peter Levi (peterlevi) wrote :

Another issue that should be resolved: the Unicode-related errors

Revision history for this message
James Lu (jlu5) wrote :

With the EOL for Python 2 being 2.5 years away, there is no reason this shouldn't be done in the long run.

Looking at debian/control, all of the libraries we use have Python 3 equivalents already:

python-bs4 -> python3-bs4
python-cairo -> python3-cairo
python-configobj -> python3-configobj
python-dbus -> python3-dbus
python-gi-cairo -> python3-gi-cairo
python-pil -> python3-pil
python-pycurl -> python3-pycurl
python-requests -> python3-requests

Changed in variety:
importance: Low → Medium
James Lu (jlu5)
summary: - Evaluate if porting to Python 3 is a good idea
+ Port to Python 3
James Lu (jlu5)
Changed in variety:
status: Triaged → Fix Committed
assignee: Peter Levi (peterlevi) → nobody
Revision history for this message
James Lu (jlu5) wrote :

Fixed in 0.7.0

Changed in variety:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.