> On Aug 24, 2015, at 5:37 PM, Carl Meyer <c...@oddbird.net> wrote: > >> Any ideas on alternative ways to tackle this? I'm officially stuck. > > I'm afraid I don't have any solution to offer, other than embracing the > "abstract vs concrete" dependencies distinction, and accepting the fact > that users of your wheels/eggs are choosing to be more "on their own" > when it comes to their chosen dependency versions.
I definitely agree. setup.py files, for the reason you mentioned, are not intended for concrete dependencies, while requirements.txt files are. They are the right tool for the job. If I was you, that's what I would do. -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/486DA079-7F97-4597-A7FB-CD179DFB54DC%40ryanhiebert.com. For more options, visit https://groups.google.com/d/optout.
