Currently, using the "Save as new" button will redirect to the list view,
while it would be more useful for it to redirect to the newly created item.
This also makes it much easier to create a series of new objects where the
next one only differs slightly from the last one.
There is a ticket for t
I've picked up this old ticket:
https://code.djangoproject.com/ticket/56
After some initial discussions on #django-dev it seems like wontfixing it
would be an option too, so I wanted to ask about core devs' view on this:
Is implementing opt-in support for unsigned primary keys on MySQL still
int
jango Software Foundation needs to build a service
>> like that.
>>
>>
>> On Thursday, June 4, 2015 at 11:08:01 AM UTC-4, Markus Amalthea Magnuson
>> wrote:
>>>
>>> Had discussions on an idea during DjangoCon Europe that I thought I'd
>>> ju
Another idea spawned during DjangoCon Europe:
Would it make sense to have more non-technical components in Trac? I'm
thinking of e.g. "Inclusion" that tracks how the project presents itself to
new users, "Diversity" for tracking improvements to various such aspects,
etc. etc. These are just a c
Had discussions on an idea during DjangoCon Europe that I thought I'd just
throw out there on this list as well:
What if the Django project provided free hosting for small projects, so
that any newcomer who went through the tutorial or similar could actually
deploy their application somewhere i
Which is, I guess, why it is the block tag's behavior that would need to
change rather than the if tag's, if support for blocks inside if tags were
to be implemented.
Have not had a look myself at this though, but I too was confused the first
few times I tried to put blocks in if statements and no
, inconsistent syntax
>> in its built-in tags. I don’t like the idea of adding more.
>>
>> We have to balance saving keystrokes against increasing the amount of
>> things every Django user needs to know. In this regard, adding that new
>> syntax looks like a bad tradeo
Hey all,
Tim Graham suggested I posted to this list regarding an idea for a new
feature: conditional block tags.
I've summarized the feature in this
ticket: https://code.djangoproject.com/ticket/24232
The basic idea is to be able to write something like this in a template:
{% block myblock if
