Code

Opened 3 years ago

Closed 3 years ago

#16475 closed New feature (duplicate)

Django needs to support python 3

Reported by: kaasib@… Owned by: nobody
Component: Uncategorized Version: 1.3
Severity: Normal Keywords:
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Django needs to support python 3, as many developers like me are not going to do their next portal and apps. in django because we fear that after some time we will need to rewrite our code for python 3. So it should support python 3 asap.

Attachments (0)

Change History (1)

comment:1 Changed 3 years ago by aaugustin

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Resolution set to duplicate
  • Status changed from new to closed

Given the amount of work required to port Django to Python 3, it isn't necessary to have a ticket in Trac. That's not the kind of thing you do "asap". See also #10998.

I'd like to mention that in this community, we expect everyone to do at least a quick search before rushing to Trac. Given your message, you've apparently never used Python, and you listened to FUD instead of reading about the current efforts to port Django to Python 3 — there are branches, core developers blog posts, etc. — and the migration path from Python 2 to Python 3 (2to3, etc.)

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.