Arthur Koziel wrote: > Here's how I thought of it (using hashlib as an example): > > Once the python25 port is updated, the hashlib module will be located > one level > above the "site-packages" directory. So, all "import hashlib" > statements would > result in importing the hashlib module installed by python25, not the > one installed > by py25-hashlib. > > There would still be ports depending on py25-hashlib but they would > work fine. > We could remove the dependency on py25-hashlib from other ports one by > one > and then finally remove py25-hashlib. > > Is this correct, or do I miss something obvious here?
I didn't know the integrated module would be installed into another directory. If python25 and py25-* would not conflict on any files, this will work. Rainer _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
