PyPI packages 'static' and 'dj-static' might help you.
--
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
+1 for is_installed
Aymeric, thanks for your work
--
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
On Friday, December 6, 2013 11:36:00 AM UTC-3, unai wrote:
>
> Lot of app/CMS creators create base templates for their apps. Currently,
> if one
> of those templates needs some kind of change, the user needs to copy the
> template all over again, making it difficult to update their templates
>
I had the same confusion that you seem to have. There is a difference
between application namespace and instance namespace. Because usually you
only have one instance of each of the installed apps, you don't need to
pass `current_app=mycoolappname_instanceX`.
In the case of multiple admin
>
> On Thursday, November 14, 2013 12:55:32 PM UTC-3, Amirouche Boubekki wrote:
>>
>>
>> 2013/11/14 Florian Apolloner
>>
>>> We might have to fix the docs there :)
>>>
>>
>> It's was fixed somewhat [1]. ...
>>
>
>
I think Florian refers to other part, which is indeed
t; templates; which is good since you really don't want to change string
> there… When you need to refer to the "other" admin just pass
> current_app='other_admin' to reverse.
>
> Chers,
> Florian
>
> On Thursday, November 14, 2013 1:55:13 AM UTC+1, German Larrai
Hi guys
I must say I hit this issue a few months ago (I have more than one admin
app living side by side). It was confusing, when reversing a URL name,
whether to change 'admin' in a string like this `'admin:%s_%s_change'`, or
use `current_app=self.admin_site.name`.
Since I don't like
> Use double quotes for strings meant for human consumption, use single
> quotes for everything else.
>
> Text, trans strings, model verbose_names: double quotes
> Dict keys, HTML tags, flags, and similar: single quotes
>
> Use triple quotes for long blocks of text, ideally only necessary
FWIW I was very surprised when I realized this problem. I couldn't understand
why a model object with an email field (without `blank=True`) could be saved
with an empty string as email address.
The way I dealt with this was creating a mixin (ValidateModelMixin) and adding
it as left-most
BTW, the URLs
http://blog-amirouche.dotcloud.com/notes/2013/admin-next-a-new-api.html
http://amirouche.github.io/blog/django-admin-next-a-new-api.html
lead to 404s.
The correct one is
http://www.hypermove.net/notes/2013/admin-next-a-new-api.html
On Saturday, March 30, 2013 5:49:27 PM UTC-5,
I know there are different opinions on this topic but if anyone is
interested, I created a repo for the tutorial. The idea is to have branches
and tags that match those of the documentation.
https://github.com/glarrain/django-tutorial-source-code
A nice advantage of that is to be able to
Hi Stan.
I'm currently looking for "admin-related" features that seemed to be kind
of accepted by the core developers.
What's the status of your proposal for grouping actions?
Best regards,
Germán Larraín
On Thursday, March 28, 2013 8:51:10 AM UTC-5, Stan wrote:
>
>
>
> On Thursday, March 28,
12 matches
Mail list logo