Bug #16278
closed
zypper_pattern module does not work in python3
Added by Félix DALLIDET about 5 years ago.
Updated over 2 years ago.
Description
Still true, we are opening the output from some commands as "text" and not "bytes" since we are using the universal_newlines type in a function.
- Related to Bug #15522: zypper_pattern module does not work in python3 added
- Status changed from New to In progress
- Assignee set to Félix DALLIDET
This only affect the zypper_pattern module, mostly because it is the only module which call cmd based on other cmd outputs.
Since python3, bytes and str are separated and we must pass on every string manipulation previously done and update them to be sure they never mix bytes and str.
Bytes are mostly coming from cmd outputs, but in some cases, the cmd output outputs str, I think the "universal_newline" option it the faulty member here.
- Target version changed from 6.0.0 to 6.0.1
- Target version changed from 6.0.1 to 6.0.2
- Status changed from In progress to Pending technical review
- Assignee changed from Félix DALLIDET to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/ncf/pull/1132
- Status changed from Pending technical review to Pending release
- Fix check changed from To do to Checked
- Subject changed from zypper_pattern module does not work in python3 Bis to zypper_pattern module does not work in python3
- Name check changed from To do to Reviewed
- Status changed from Pending release to Released
This bug has been fixed in Rudder 6.0.2 which was released today.
- Project changed from 41 to Rudder
- Category changed from Generic methods - Package Management to Generic methods
Also available in: Atom
PDF