On Dec 4, 2013, at 4:31 PM, Florian Apolloner <f.apollo...@gmail.com> wrote:
> Oh, one last thing (a few actually): > How does 'entry_points' work with wheels? > Do we need an extra wheel for windows just to get the wrappers right? > Can we generate a windows wheel from *nix, or do we need a windows box? entry points are kinda wonky with pip 1.4, pip 1.5 makes them sane. You would not need a Windows specific Wheel with pip 1.5 > Cheers, > Florian > > > On Wednesday, December 4, 2013 10:24:09 PM UTC+1, Florian Apolloner wrote: > > > On Wednesday, December 4, 2013 8:24:49 PM UTC+1, Remram wrote: > December 4 12:43, Florian Apolloner > To my understanding of > https://github.com/pypa/pip/blob/develop/pip/req.py#L633 pip will use > setuptools for installing -- so why do you need setuptools in Django itself? > The point here is to use options that distutils doesn't offer, like > entry_points, if they are available. > > Ah, I assumed that the workaround you mentioned would be setuptools just > wrapping everything in 'scripts' -- didn't know that you'll have to use > 'entry_points' then. > > Also (refering to your first post), why is associating stuff with .py files a > bad idea? > I personally have .py files associated with my text editor. Defaulting them > to the system-wide Python 2.7 might do the correct thing in some cases... > > Oh, that makes sense I guess :) > > Associating .py files with Python is not enough -- only binaries are searched > for in the PATH when typing a path-less command name (.com, .exe, .bat and a > few others). > > Okay, that's just horrible! > > Which downsides does using 'entry_points' have for a *nix based system? I'd > rather not support disutils and setuptools; this just calls out for pain. My > last worry (probably needlessly) is that we might run into issues with one of > the hundred setuptools versions out there; all together there is distribute, > old setuptools, new setuptools and whatever distris like debian packaged > currently -- I don't think most users upgrade setuptools that often, so are > there any issues to be expected with stoneold setuptools? [Granted, that's > not really our problem, but if we know of some issues we could warn the users] > > Cheers, > Florian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" 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 http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/f3195fb1-1505-41ce-b34a-0cf147f33e1f%40googlegroups.com. > For more options, visit https://groups.google.com/groups/opt_out. ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail