Bug 1285500

Summary: AttributeError: module 'html.parser' has no attribute 'HTMLParseError'
Product: [Fedora] Fedora EPEL Reporter: Mairi Dulaney <jdulaney>
Component: python-djangoAssignee: Matthias Runge <mrunge>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: epel7CC: bkabrda, jal233, jdornak, mhroncok, michel, mrunge
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-11-26 14:58:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
htmlparseerror.patch none

Description Mairi Dulaney 2015-11-25 19:08:47 UTC 
Created attachment 1098939 [details]
htmlparseerror.patch

Description of problem:
When building on for python 3.5, I get the following error:

AttributeError: module 'html.parser' has no attribute 'HTMLParseError'

Version-Release number of selected component (if applicable):
1.6.11

How reproducible:
Always

Steps to Reproduce:
Build using python 3.5

Actual results:
Build fails

Expected results:
Build completes

Additional info:
This is a known issue with django that has been fixed upstream(0).  Accordingly, would it be possible to apply the (attached) patch to the epel package?


(0)  https://github.com/django/django/commit/b07aa52e8a8e4c7fdc7265f75ce2e7992e657ae9


PS, yes, I know epel doesn't officially support python 3.5, but this is for my own project.
Comment 1 Mairi Dulaney 2015-11-25 19:32:13 UTC 
You know instead, make this a request to update to the latest django in epel7.  If you can't do that, then let me know and go ahead and close this here ticket.
Comment 2 Matthias Runge 2015-11-26 07:47:41 UTC 
Unfortunately I can't update to 1.8.x, as for example reviewboard requires Django-1.6.
I will look into cherry-picking above commit, as we're already carrying several patches.

If you want Django-1.8, you should be able to pick it from CentOS cloud repository, OpenStack Kilo (or later) runs on Django-1.8; admitted, that's python2-django, no python3 version.
Comment 3 Mairi Dulaney 2015-11-26 14:58:20 UTC 
I built from the latest srpm in Fedora; we can go ahead and close this.