I just ran into a interessting variant of this bug. It seems to be important in what order the packages get installed for them to be byte-compiled (done on a current jaunty chroot):
I think this will be fixed with the new python-central upload that fixes (#357884).
But there is still the inconsitency that the rtinstall scripts are not run when the new 2.4 runtime
gets installed (because of:
if ! grep -sq '^supported-versions[^#]*python2.4' /usr/share/python/debian_defaults
But if a package gets (re)installed then pycentral creates the links for it. If its intentional, I find
it confusing :)
I just ran into a interessting variant of this bug. It seems to be important in what order the packages get installed for them to be byte-compiled (done on a current jaunty chroot):
[chroot1] distutils- extra python2. 4/site- packages/
# apt-get install python-
# apt-get install python2.4
# ls /usr/lib/
README
[chroot2] distutils- extra python2. 4/site- packages/ distutils_ extra-0. 90.egg- info
# apt-get install python2.4
# apt-get install python-
# ls /usr/lib/
DistUtilsExtra README python_
I think this will be fixed with the new python-central upload that fixes (#357884).
But there is still the inconsitency that the rtinstall scripts are not run when the new 2.4 runtime versions[ ^#]*python2. 4' /usr/share/ python/ debian_ defaults
gets installed (because of:
if ! grep -sq '^supported-
But if a package gets (re)installed then pycentral creates the links for it. If its intentional, I find
it confusing :)