Code

Opened 6 years ago

Closed 6 years ago

#6912 closed (duplicate)

get rid of robusapply.py

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

Description

django/dispatch/robustapply.py contains horrible logic (some duck typing) for checking differences between builtin methods and normal methods (or something like that). This is pretty implementation-specific and makes django choke on top of pypy. I think it's still django bug to rely on such obscure details. What do you think?

Attachments (0)

Change History (2)

comment:1 Changed 6 years ago by ramiro

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

See #4561, #6814, #6857 and recent related django-developers mailing list threads about ongoing work in this area.

comment:2 Changed 6 years ago by ubernostrum

  • Resolution set to duplicate
  • Status changed from new to closed

Closing as a dupe since this has already come up and is being dealt with. In the future, please search before opening a new ticket.

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.