Bug 84966 – path in byte-compiled code still wrong

Bug 84966 - path in byte-compiled code still wrong

Summary:	path in byte-compiled code still wrong

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	python (Show other bugs)
Sub Component:
Version:	9
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Mihai Ibanescu
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2003-02-24 09:12 EST by Mihai Ibanescu
Modified:	2008-01-17 12:49 EST (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-08-04 16:35:43 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Mihai Ibanescu 2003-02-24 09:12:19 EST

Description of problem:
There is still a bug in the code that cleanses the path of the bytecode-compiled
files.

python -c 'import xmlrpclib; xmlrpclib.loads("adsfadf")'
Traceback (most recent call last):
  File "<string>", line 1, in ?
  File "//usr/lib/python2.2/xmlrpclib.py", line 805, in loads
    p.close()
  File "//usr/lib/python2.2/xmlrpclib.py", line 393, in close
    self._parser.Parse("", 1) # end of data
xml.parsers.expat.ExpatError: syntax error: line 1, column 0

Notice the double-slash.

Comment 1 Mihai Ibanescu 2003-02-24 11:28:58 EST

Fixed in 2.2.2-24

Comment 2 Bill Nottingham 2006-08-04 16:35:43 EDT

Red Hat Linux and Red Hat Powertools are currently no longer supported by Red
Hat, Inc. In an effort to clean up bugzilla, we are closing all bugs in MODIFIED
state for these products.

However, we do want to make sure that nothing important slips through the
cracks. If, in fact, these issues are not resolved in a current Fedora Core
Release (such as Fedora Core 5), please open a new issues stating so. Thanks.

Note You need to log in before you can comment on or make changes to this bug.