Bug 720111 - LZMAFile does not support the with statement properly
Summary: LZMAFile does not support the with statement properly
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: pyliblzma
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: François Cami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-09 14:08 UTC by Cristian Ciupitu
Modified: 2014-01-21 23:18 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-30 17:58:53 UTC
Type: ---


Attachments (Terms of Use)
test.py (131 bytes, text/x-python)
2011-07-09 14:08 UTC, Cristian Ciupitu
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Launchpad 1219296 0 None None None Never

Description Cristian Ciupitu 2011-07-09 14:08:52 UTC
Created attachment 512044 [details]
test.py

Description of problem:
LZMAFile does not support the with statement properly.

Version-Release number of selected component (if applicable):
pyliblzma-0.5.3-5.fc15.x86_64.rpm

How reproducible:
Every time

Steps to Reproduce:
1. Run the attached file, e.g. ./test.py foo.xz
 
Actual results:
Traceback (most recent call last):
  File "./test.py", line 7, in <module>
    with tmp as f:
AttributeError: __exit__

Expected results:
No errors

Additional info:
If the dir call is uncommented, the program will work fine.

Comment 1 Cristian Ciupitu 2011-07-09 14:11:42 UTC
Errata: I uploaded by mistake the version with the dir call uncommented. Please comment it out in order to reproduce the bug.

	from lzma import LZMAFile
	import sys

	tmp = LZMAFile(sys.argv[1])
	#dir(tmp)
	with tmp as f:
	    print f.read()

Comment 2 Fedora End Of Life 2012-08-07 18:36:43 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Cristian Ciupitu 2012-08-08 08:08:55 UTC
It's still present in Fedora 17 (pyliblzma-0.5.3-6.fc17.x86_64, python-2.7.3-7.2.fc17.x86_64).

Comment 4 Fedora End Of Life 2013-07-04 06:31:41 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Cristian Ciupitu 2013-07-04 10:00:51 UTC
It's still present in Fedora 18 - pyliblzma-0.5.3-7.fc18.x86_64.

Comment 6 Fedora Admin XMLRPC Client 2013-08-30 17:35:26 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 François Cami 2013-08-30 17:58:53 UTC
This is upstream's issue, not Fedora's.
Please report to upstream at https://launchpad.net/pyliblzma
Closing.

Comment 8 Cristian Ciupitu 2013-08-31 20:05:14 UTC
I've reported it upstream https://bugs.launchpad.net/pyliblzma/+bug/1219296

Comment 9 François Cami 2013-08-31 20:41:49 UTC
Thank you. If they fix it please let me know, I'll backport the fix.


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