* On 07.07.2014 11:32 am, Peter Danecek wrote: > Why not allowing that either PIL or Pillow satisfies the dependency where > possible. > [...] > This would avoid potential conflicts if users need to install other (still) > PIL dependent software.
That would be possible, yes. But as I understood it, Pillow is a drop-in replacement for PIL and is always supposed to work with software initially written for PIL. However, I'm not a python programmer and might be wrong. My thinking was that, as Pillow is supposed to be a PIL-compatible drop-in replacement, we could avoid all problems like - package1 -> Pillow - package2 -> PIL => package1 can't be installed at the same time with package2 (and vice versa) (Note that while PIL is supposed to always be substitutable with Pillow, the other way is not possible, if specialized Pillow features are being used.) Does that make sense? Mihai
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
