Re: Proposal: FileSystemFinder and AppDirectoriesFinder shall serve unminimized assets in DEBUG mode

> On 25 Apr 2020, at 21:59, Jacob Rief wrote: > > So unless Django embraces npm in order to execute the > compile/compress/concatenate/uglify-steps, I don't see a lot of possibilities > other than referring to the processed, aka *.min.xyz file. Well, see the other thread but

Re: Proposal: FileSystemFinder and AppDirectoriesFinder shall serve unminimized assets in DEBUG mode

On Friday, April 24, 2020 at 7:21:24 AM UTC+2, Carlton Gibson wrote: > > For instance if we were to include a compression step, you’d always just > reference the raw assets, these being processed, with source maps if we had > that, for production. > It certainly is the proper approach to refer

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

I would be in favour of Adam’s proposed changes. Adding more context to them and stripping the appended timestamp would make them more user friendly. > As a developer I would like to know who generated the code. If a migration is > auto-generated, I would like to know that. I checked and auto-ge

Re: Django for beginners

Larbi, that is the roadmap for Django CMS, a separate project that is an extension to Django. Elisabetta, yes this is more of a support question. If you’re looking for learning materials, check out the awesome Django list: as a start: https://github.com/wsvincent/awesome-django On Sat, 25 Apr 202

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

On Sat, Apr 25, 2020 at 5:48 PM Adam Johnson wrote: > Re: Uri: > >> If the file name is not like ‘auto’ name with the current date + time, it >> looks like a migration which was written by a developer. >> > > I think making a distinction between "auto generated" and "hand written" > migrations is

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

Re: Uri: > If the file name is not like ‘auto’ name with the current date + time, it > looks like a migration which was written by a developer. > I think making a distinction between "auto generated" and "hand written" migrations is a bad idea. Django's makemigrations is a code generator, but as

Re: Django for beginners

Hi Elisabetta, If You age looking for a simplified roadmap of Django as a project and how it will evolve in the future there is a link https://www.django-cms.org/en/roadmap Am I answering your question? Larbi On Sat., Apr. 25, 2020, 9:24 a.m. elisabetta fierro, < fierroelisabe...@gmail.com> wrot

Re: Django for beginners

Hi! I think you've found the wrong mailing list for this post. This mailing list is for discussing the development of Django itself, not for support using Django. This means the discussions of bugs and features in Django itself, rather than in your code using it. People on this list are unlikely t

Django for beginners

Is it available a Django roadmap for beginners? -- 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

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

I’ve been in both situations more than once: 1. wanting to just run makemigrations and never look back, 2. naming each migration and reminding people to do the same. Small teams / solo = 1, Large teams = 2. Perhaps a new setting? AUTO_NAME_MIGRATIONS = None # makemigrations fails if no n

Re: Remove automatic date-naming of migrations (00XX_auto_YYYMMDD)

On Wed, Apr 22, 2020 at 4:06 PM Adam Johnson wrote: > Hi djangonauts, > > In a blog post earlier this year I outlined my technique to prevent Django > creating migration files with automatic date names. I had a lot of response > with other techniques and ended up adding two more techniques to the