Hi bro, you can use this
{% url 'home' %}
the app_name isn't the namespace, the namespace is define on the main
urls.py, if you haven't a namespace defined, so, with the name assined on
the path() is sufficient
greetings!
*Franklin
uot;.
In my opinion, either a blank app name or 'self' would be a better choice
for that special value. And it would cause a lot of issue. It might break
existing Django app, which is bad. It will make finding all references if
an URL in you code harder as you need to search for both the absolute a
Hello,
If in the urls.py, I can write:
*app_name* = '*posts*'
.
.
path(' ', views.home, name='home'),
then why it is required to refer url name (from the template) by the *app_name
value* as:
{% url '*posts*:home' %}
It should be referred instead by *app_name variable* like below:
{% url
but somewhat tedious cleanup - mostly involving backing out the metaclass
pattern for app objects.
The crux will be a way to introduce this in form that provides some
limited, targeted benefits such as the verbose app name, without opening
too much of a pandora's box of enabling a range
and at that time, it was extremely close to being ready for merging -- it
>> mostly just needed eyeballs, testing, and documentation. If you want to
>> help out, I'd suggest grabbing that code, and trying to (a) get it up to
>> date, and (b) testing it with your own projects, a
ust needed eyeballs, testing, and documentation. If you want to
> help out, I'd suggest grabbing that code, and trying to (a) get it up to
> date, and (b) testing it with your own projects, and © helping to stub out
> documentation.
>
> I'd very much like to see this patch land as p
alls, testing, and documentation. If you want to
help out, I'd suggest grabbing that code, and trying to (a) get it up to
date, and (b) testing it with your own projects, and © helping to stub out
documentation.
I'd very much like to see this patch land as part of the 1.6 cycle -- App
name trans
Ramiro, I've read the ticket but it seems stuck. I just want it to go
forward because I think it's a major UI/UX issue for non-programmers the
lack of "pretty" app names. But I want it to be done right with a proper
app metadata handling.
The thing is that there isn't any consensus about the
On Fri, Dec 7, 2012 at 11:18 AM, Aymeric Augustin
wrote:
> FYI the latest efforts on this topic are here:
> https://github.com/ptone/django/compare/app-loading
> http://code.djangoproject.com/ticket/3591
Exactly,
The issue described in this thread is already
I read the tickets. Many are outdated and the approach in the trac ticket
below I believe it's not very well defined. About putting app names on the
INSTALLED_APPS, I don't think it would be good for packaging. That's why I
believe it should be somewhere on the app itself. About using admin.py
FYI the latest efforts on this topic are here:
https://github.com/ptone/django/compare/app-loading
http://code.djangoproject.com/ticket/3591
--
Aymeric.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
This is important not only for internationalization, but also for English
app names, consisting of several words. Neither Siteconfig nor Site_config
look pretty.
I think that app name should not be defined as a static variable in
__init__.py file for this reason: if we want to translate the label
As an alternative to creating AppConfig class, what about registering app
names, just like we register ModelAdmin instances:
admin.site.register_app_label("myapp", _("My awesome web app"))
- Sergiy
On Thu, Dec 6, 2012 at 11:57 PM, Pedro J. Aramburu
wrote:
> As I
As I explained on the Django users forums (
https://groups.google.com/forum/?fromgroups=#!topic/django-users/ZUxZHi_-5ug)
I'm spanish speaking so my users are too. Writing code in spanish isn't
pretty and with characters like "á" or "ñ" it's very difficult to name the
apps a way that would make
On 9/18/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Is there a reason why the app name doesn't appear in the admin
> breadcrumbs? I have an app with a model called 'Groups', and the
> breadcrumb for it is the same as that for the auth model 'Groups'. The
> URL is rig
Is there a reason why the app name doesn't appear in the admin
breadcrumbs? I have an app with a model called 'Groups', and the
breadcrumb for it is the same as that for the auth model 'Groups'. The
URL is right, of course, I just thought it might be sensible to stick
the app name in there, so
16 matches
Mail list logo