Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 985295 - python-pyblock Python 3 compatibility
Summary: python-pyblock Python 3 compatibility
Keywords:
Status: CLOSED DUPLICATE of bug 1014581
Alias: None
Product: Fedora
Classification: Fedora
Component: python-pyblock
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Peter Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: PY3ANACONDA
TreeView+ depends on / blocked
 
Reported: 2013-07-17 09:17 UTC by Bohuslav "Slavek" Kabrda
Modified: 2013-10-02 11:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-02 11:14:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bohuslav "Slavek" Kabrda 2013-07-17 09:17:42 UTC
Hi,
is there any plan/estimate of making python-pyblock compatible with Python 3? I'm currently trying to figure out what it'd take to move Fedora to Python 3 and since python-pyblock is one of Anaconda's deps, it'd need to be converted as one of the first.
Thanks.

Comment 1 Fedora End Of Life 2013-09-16 14:33:41 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 20 development cycle.
Changing version to '20'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora20

Comment 2 Miro Hrončok 2013-10-01 14:33:57 UTC
If you need any extra hand with this, feel free to use me :)

Comment 3 Miro Hrončok 2013-10-02 11:14:55 UTC
Sorry, I accidentally created this again. Marking this as duplicate, as the other one has more info.

*** This bug has been marked as a duplicate of bug 1014581 ***


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