> On Apr 7, 2016, at 1:31 AM, Sylvain Fankhauser <sylvain.fankhau...@gmail.com> > wrote: > > The only problem I can see is dependencies conflicts, where Django would need > package X version > 1.0 and another installed package would need package X > version 0.9. I have this issue with a project of mine that required six >= > 1.10 and for some reason Xcode on OSX with the system Python (ie. not > installed with brew for example) forces you to have six 1.9, which comes > before in the PYTHONPATH. I know that Lektor <https://www.getlektor.com/> for > example solves this by having an install script > <https://www.getlektor.com/install.sh> that creates a virtualenv and installs > it inside this virtualenv. > Yea. This is a problem with OS X Python from the system. They ship a bunch of libraries that are on the sys.path by default but which can’t be replaced (even more so in the most recent version of OS X when SIP is turned on which prevents installing anything into the system Python as well). This issue has been reported to Apple and I think there is a good chance that they’ll have it fixed in a way that a user can install packages into.
Overall though, users shouldn’t install things into their system Python which I think is supported by the fact that the system Python on recent versions of OS X are not writable, even with sudo, unless you disable one of the major security components of your machine. That doesn’t affect just any potential dependencies Django might have, but also Django itself. > Also James mentioned that "back in the days pip wasn't as awesome as it is > today", but we have to keep in mind that a lot of OSes still use an old pip > version by default (Debian stable for example ships pip 1.5 > <https://packages.debian.org/search?keywords=python-pip&searchon=names&suite=stable§ion=all>). > pip 1.5 is new enough that you get most of the reliability benefits. Major things it’s missing are: * Implicit wheel cache, allowing sdists to only be compiled once and the built binaries reused between installs. * Implicit http cache, allowing files to only need to be downloaded once. * Manylinux1 support, allowing people to publish binary wheels for Linux systems to PyPI. * Conditional dependencies inside of a sdist without a hack workaround. Minor, but nice quality of life things are: * Massively reduced verbosity on install. * Nicer progress bars. > Anyway as long as Django is installed in a virtualenv this shouldn't be too > much of an issue, but I think we should expect some issues from the users and > these should be documented otherwise people might get frustrated. > > Cheers, > Sylvain > ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CCC99F08-1813-4E09-AE4B-B5E4BF58F618%40stufft.io. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
