Hi Aleksej, Thanks for your work on this, and sorry I haven't replied sooner -- just been busy with lots of other things ;)
My plan for integrating WhiteNoise was actually to merge it in as part of contrib.staticfiles and basically stop development on it as an independent project. When I first started WhiteNoise I went to quite a lot of effort to make the core framework-agnostic and to have all the Django specific code as an extension to the core. However this makes the code more complex than if it was written for Django alone. I'm also not sure it gets a lot of use outside of the Django world as other frameworks have their own way of doing things and the most useful features of WhiteNoise are Django only. So the end-goal in my mind is to have a stripped down and simplified version of the WhiteNoise code bundled as part of Django itself, which I could then help maintain as part of the wider Django project. However, I don't think this process would be an ideal project for someone who is a new contributor to Django as it would require quite a detailed understanding of the design decisions and architectural tradeoffs behind WhiteNoise. Really this is the sort of thing I ought to be doing but it's been quite a busy year (new baby, work, etc etc) and I just haven't had the time. If you're able to bundle WhiteNoise as it currently is with Django in a way that the core devs are happy with then that's great, and obviously I wouldn't stand in your way. But I can imagine that there might be some resistance to creating a hard dependency on WhiteNoise, while it's still a standalone project. Again, thanks for the work you've put into this and sorry I don't have a more helpful response. Dave On Wednesday, 22 March 2017 16:14:58 UTC, Aleksej Manaev wrote: > > Am I on the right track with the integration of WhiteNoise into Django? > Can Someone lead me to the next steps that need to be done? > > > https://github.com/django/django/compare/master...AleksejManaev:ticket_27325?expand=1 > > I think "django/views/static.py" can't be deprecated because it is used > for providing MEDIA_FILES during development and WhiteNoise is only > responsible for STATIC_FILES. > -- 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 [email protected]. To post to this group, send email to [email protected]. 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/cfbf04a4-9346-4fd7-95bf-e3802f7a8e5d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
