On Wed, Aug 13, 2014 at 3:59 AM, Russell Keith-Magee
<russ...@keith-magee.com> wrote:
> As I see it, you have four options:
there's also option #2.5:
* distribute .pyc files as required, but include a call to uncompyle2
(or any alternative .pyc to .py decoder) at setup time, so Django
finds the .py files as usual.
it not only follows the letter of the requirement ("thou shalt not
give your .py files unto others"), but highlights how inappropriate it
is.
--
Javier
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/CAFkDaoQrXybRDCLr05F-DsZ-wBrUzq2Zz6YnW6omUDegunJcmg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
