On Saturday 19 December 2009 19:27:10 Lucas C. Villa Real wrote: > Hi there, > > I was compiling some packages for 015 tonight when I realized that, > after having built Python 3.1.1, some of our scripts started to fail > to execute. What's the idea for 015? Are we going to stay with Python > 2 and allow for users to install Python 3 by themselves or will we > rewrite our Python scripts to meet the API changes? They (ought to) only ever run against Python 2 anyway; unless you `make fullinstall`, which the recipe doesn't, the python->python3.1 link isn't created. I don't know what's causing your problem, but it isn't that. It's an entirely orthogonal installation.
When I think, I guess it's because ChrootCompile included the newest package and no Python 2 at all in the environment. The Scripts dependencies should be updated to put an upper limit on it, if ChrootCompile obeys them. Otherwise the Python 3.1.1 package should be blocked. Scripts will depend on Python 2 for the foreseeable future, but in the long run we should fix them up. -Michael
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
