I found the culprite, the conf.py file of the documentations prepend ".." to 
sys.path befor importing the module.
This is why it use the wrong version of the built module.


Now during the build I have this

D: dh_python3 dh_python3:164: args: []
D: dh_python3 dh_python3:166: supported Python versions: 3.6,3.7 (default=3.6)
D: dh_python3 debhelper:107: skipping package: python-uncertainties
D: dh_python3 debhelper:153: source=uncertainties, binary 
packages=['python3-uncertainties']
D: dh_python3 dh_python3:183: processing package python3-uncertainties...
D: dh_python3 fs:49: moving files from 
debian/python3-uncertainties/usr/lib/python3.6/dist-packages to 
debian/python3-uncertainties/usr/lib/python3/dist-packages/
D: dh_python3 fs:49: moving files from 
debian/python3-uncertainties/usr/lib/python3.7/dist-packages to 
debian/python3-uncertainties/usr/lib/python3/dist-packages/
W: dh_python3 fs:98: Paths differ: 
debian/python3-uncertainties/usr/lib/python3.7/dist-packages/uncertainties/core.py
 and 
debian/python3-uncertainties/usr/lib/python3/dist-packages/uncertainties/core.py
W: dh_python3 fs:98: Paths differ: 
debian/python3-uncertainties/usr/lib/python3.7/dist-packages/uncertainties/lib1to2/test_1to2.py
 and 
debian/python3-uncertainties/usr/lib/python3/dist-packages/uncertainties/lib1to2/test_1to2.py
W: dh_python3 fs:98: Paths differ: 
debian/python3-uncertainties/usr/lib/python3.7/dist-packages/uncertainties/umath_core.py
 and 
debian/python3-uncertainties/usr/lib/python3/dist-packages/uncertainties/umath_core.py
D: dh_python3 fs:246: package python3-uncertainties details = {'requires.txt': 
{'debian/python3-uncertainties/usr/lib/python3/dist-packages/uncertainties-3.0.2.egg-info/requires.txt'},
 'egg-info': set(), 'nsp.txt': set(), 'shebangs': set(), 'public_vers': 
{Version('3'), Version('3.7')}, 'private_dirs': {}, 'compile': True, 
'ext_vers': set(), 'ext_no_version': set()}



I am worried by the dh_python3 warnings.
It seems that the 2to3 files generated  by python3.6 and python3.7 differ.

I am right ?, and then what is the right way to solve this issue ?


thanks


Frederic

Reply via email to