Are you using Python 3?

  • 9 votes.
  • Posted by rafalp on July 4, 2018.
8 votes, 88% of total.
  • 8 votes, 88% of total.
No, but I want to move
0 votes, 0% of total.
  • 0 votes, 0% of total.
1 vote, 11% of total.
  • 1 vote, 11% of total.
  • July 4, 2018, 6:36 p.m.

    It's been a while but now I feel that its time to start thinking about dropping Python 2.7 support in Misago. For long time the primary argument against this was "there's still number of great libs and tools that are python 2.7 only", but this has turned around. Today Python 3 is the language that cool crowd uses, and major libraries have either made the move or were superset by new solutions.

    I would also like to make Misago Python 3-only. This change would not happen tomorrow, or in next release, but I would like it to happen sometime during this year.

    I am also pleased with Django 1.11, and would like to stay on LTS until next one, so we would likely have transition period where Misago requires Django 1.11 and Python 3.4+ to run.

  • bookmark

    Thread has been pinned globally.

  • July 4, 2018, 11:52 p.m.

    Getting over to Django 2.x is definitely a good idea in the long run. I suspect 1.11 will become a bit stale feature wise pretty soon. They are planning to support 1.11 for a long time afaik.

  • July 5, 2018, 12:35 p.m.

    Going stale is part of the plan I guess. I understand that developers want to use latest and greatest but keeping track of Django releases was really tiring for me when maintaining Misago, and moving to LTS was great relief.

    Next LTS will be Django 2.2 which is expected to be released on April 2019, but Django 2.0 is promised to receive fixes until that happens, so moving from 1.11 LTS to 2.0 may be an option too.

  • Members 1 post
    July 10, 2018, 8:18 a.m.