Re: Digest for django-developers@googlegroups.com - 17 Messages in 3 Topics
Quoting django-developers@googlegroups.com (2013-05-31 07:39:24) > From: Andrew Godwin > Date: May 30 07:03PM +0100 > Url: http://groups.google.com/group/django-developers/msg/137ab14f361fd052 > > 2. Leave syncdb as it is, like South does, and have everything happen > through a "migrate" command. Leads to weird interactions where each command > knows about the other, and must be run in a certain order, but which isn't > immediately obvious. Order in which syncdb and migrate should be run also depends on dependencies between apps. For example, if you have two apps, A and B: # A/models.py class A(models.Model): name = models.CharField(max_length=128) # B/models.py class B(models.Model): name = models.CharField(max_length=128) aref = models.ForeignKey(A) Then, first you must run syncdb/migrations for A app, and *only* then for app B. So to fully fix migrations, Django should be aware about dependencies between apps, which is very important not only for migrations. -- Mantas aka sirex __o /\ _ \<,_ -- launchpad.net/~sirex -- /\/ \ ___(_)/_(_)_/_/\ ^ -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Fixing broken internationalization in Django admin
Hi, during EuroPython Django sprint I was working with this: https://code.djangoproject.com/ticket/11688 I hope this is a right place to discuss such things. After doing some research I come to this solution: https://code.djangoproject.com/ticket/11688#comment:7 Currently I'm not implemented anything, before implementing it, I need to here from you is this is acceptable way, to fix internationalization for dynamic objects, such as models, app labels, etc. -- Mantas aka sirex __o /\ _ \<,_ -- launchpad.net/~sirex -- /\/ \ ___(_)/_(_)_/_/\ ^ -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
Re: Feature proposal: escape hatch for colliding template syntax in django templates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I propose this solution: {!x x} Or at least: {% verbatim x %} {% x %} Where 'x' can be replaced by any other string: {!! {!x x} !} {!xx {!x x} xx} {!maystring {!x x} maystring} {% verbatim - %} {% verbatim x %} {% x %} {% - %} For example, this:: {!! {% block content %} {% endblock %} !} or {% verbatim - %} {% block content %} {% endblock %} {% - %} Will be parsed as:: {% block content %} {% endblock %} This proposal is very similar to heredoc [1]: << EOF some content EOF [1]: http://en.wikipedia.org/wiki/Here_document - -- Mantas aka sirex __o /\ _ \<,_ -- launchpad.net/~sirex -- /\/ \ ___(_)/_(_)_/_/\ ^ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1N228ACgkQrRc2Mrd7P8X/OACfSXLl7/Z8z0CULLIFsDcUXoZW x40AoJZK4s5IfEeTG6u3nE/Uk+ekYEII =/QkB -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.