Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • R roomlist
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 23
    • Issues 23
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • SRCT
  • roomlist
  • Issues
  • #47

Closed
Open
Created Oct 18, 2015 by Daniel W Bond@dbond2Developer

prepare to upgrade to python 3

make sure that you include the django requirements for this as well-- see this page for details in that regard: https://docs.djangoproject.com/en/1.7/topics/python3/

doesn't require any special imports, django should handle this for you

The same code runs both on Python 2 (≥ 2.6.5) and Python 3 (≥ 3.2), thanks to the six compatibility layer.

the general python future imports:

from __future__ import division / versus //... shouldn't really impact us

this is the one I'm most concerned would break things: from __future__ import unicode_literals

would at minimum require changes from __unicode__ to __str__: see the above link for the extra methods

already completed: (though double-check)

from __future__ import absolute_import wrap multiline imports with parentheses

from __future__ import print_function add yourself some ()s

Assignee
Assign to
Time tracking