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 1738110 - python-impacket depends on Python 2
Summary: python-impacket depends on Python 2
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: python-impacket
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Michal Ambroz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 1676844 F31_PY2REMOVAL 1760138 1760139
TreeView+ depends on / blocked
 
Reported: 2019-08-06 13:05 UTC by Lumír Balhar
Modified: 2019-10-12 09:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-12 09:22:33 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Lumír Balhar 2019-08-06 13:05:25 UTC 
Python 2.7 will reach end-of-life in January 2020, over 9 years after it was released. This falls within the Fedora 31 lifetime.
Packages that depend on Python 2 are being switched to Python 3 or removed from Fedora: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages
Python 2 will be retired in Fedora 32: https://fedoraproject.org/wiki/Changes/RetirePython2

To help planning, we'd like to know the plans for python-impacket's future. Specifically:


- What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) 

- What are the upstream/community plans/timelines regarding Python 3?

- What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?)


This bug is filed semi-automatically, and might not have all the context specific to python-impacket.
If you need anything from us, or something is unclear, please mention it here.

Thank you.
Comment 1 Ben Cotton 2019-08-13 16:47:23 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.
Comment 2 Lumír Balhar 2019-08-15 06:55:09 UTC 
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.
Comment 3 Lumír Balhar 2019-08-22 07:10:01 UTC 
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.
Comment 4 Lumír Balhar 2019-08-29 05:27:31 UTC 
Please answer the above questions. If you don't, the package can be orphaned: https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages

If you need any information or help, or if you need some more time, please let us know.
Comment 5 Miro Hrončok 2019-09-05 10:41:23 UTC 
According to the procedure described in https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal#Information_on_Remaining_Packages the package was now orphaned. If you think it was a mistake, you can provide the answers and claim the package back.

Let us know if you need any help or just need more time.
Comment 6 Michal Ambroz 2019-09-19 13:46:09 UTC 
Hello,
We have already discussed this topic in April. Orphaning the package for Fabian not responding is just silly.
I would like to claim the package back if Fabian is not available.


> - What is the reason for the Python2 dependency? (Is it software written in Python, or does it just provide Python bindings, or use Python in the build system or test runner?) 
Upstream has plans to switch to python3, but it is not working well yet with the current stable release 0.9.19


>- What are the upstream/community plans/timelines regarding Python 3?
Plan is to have it ready before python2 is deprecated - ie for the next release 0.9.20
https://github.com/SecureAuthCorp/impacket/issues/663

>- What is the guidance for porting to Python 3? (Assuming that there is someone who generally knows how to port to Python 3, but doesn't know anything about the particular package, what are the next steps to take?)
It is not easy task as it was implementing many binary protocols using strings, which needs to be translated to binarrays.
I believe it is better task for upstream.

Michal Ambroz
Comment 7 Michal Ambroz 2019-09-26 12:53:06 UTC 
Upstream just released the 0.9.20 release with support for python3. 
Working on packaging it.
Comment 8 Lumír Balhar 2019-10-04 12:26:48 UTC 
Anything new here?
Comment 9 Miro Hrončok 2019-10-06 12:58:15 UTC 
I've talked to Michal in person during LinuxDays in Prague. The spec needs adapting, preferably to work single-spec an all versions. His time to work on this is limited, so maybe we can send a PR if we want to unblock pyOpenSSL.
Comment 10 Miro Hrončok 2019-10-09 23:39:55 UTC 
https://src.fedoraproject.org/rpms/python-impacket/pull-request/2
Note You need to log in before you can comment on or make changes to this bug.