Re: Proposal: Django URL Admin (django-urls)

178 views
Skip to first unread message

Florian Apolloner

unread,
Dec 7, 2012, 4:45:59 PM12/7/12
to django-d...@googlegroups.com, Zach Borboa
Hi Zach,

On Friday, December 7, 2012 9:07:32 PM UTC+1, Zach Borboa wrote:
Does something like this exist already? If not, it should.

I am wondering what you are trying to achieve with this post. If you only want to know if something like this exists you should ask in django-users, this mailing list is to discuss the development of Django itself.

If you are suggesting that we should implement it if it doesn't exist already, I would ask you to reread your email again and think about how it might sound to others or how it's perceived by others. Don't get me wrong, ideas are always good but there are differences in the ways of how ideas are presented -- especially if you want this feature you'd need to convince us why we would need something like this and your initial posting does a pretty bad job in achieving this goal. Also, if it "should" exist according to your opinion feel free to provide patches :)

Best regards,
Florian

Zach Borboa

unread,
Dec 7, 2012, 5:55:10 PM12/7/12
to Florian Apolloner, django-d...@googlegroups.com
Hi Florian,

Thank you for the response. This was just an idea and I'm glad you
welcome it. I will work on a patch and my convincing techniques.

Would something like this be better as an application (e.g.
django-urls) or part of the core?

Regards,
Zach

Jacob Kaplan-Moss

unread,
Dec 7, 2012, 6:40:53 PM12/7/12
to django-developers
On Fri, Dec 7, 2012 at 4:55 PM, Zach Borboa <zachb...@gmail.com> wrote:
Would something like this be better as an application (e.g.
django-urls) or part of the core?

As a general rule you'll *always* better off building something external. The path to getting something built-in requires overwhelming evidence that this is useful to a vast majority of Django users, and proving that without an existing codebase and (more importantly) user base is nearly impossible.

Good luck,

Jacob

Zach Borboa

unread,
Dec 13, 2012, 11:54:53 AM12/13/12
to django-d...@googlegroups.com, Zach Borboa
For those of you following, development of django-urls has moved to github. Thanks
https://github.com/django-urls/django-urls

Amirouche B.

unread,
Dec 15, 2012, 12:31:34 AM12/15/12
to django-d...@googlegroups.com, Zach Borboa


On Friday, December 7, 2012 9:07:32 PM UTC+1, Zach Borboa wrote:
Does something like this exist already? If not, it should.

How this can be useful ? You still need to write the view in Python then why not write the urls in Python too, like it's currently the way to go.

If something in this spirit might be useful is something where the view could be generated which would be something like databrowser or admin.

Could you elaborate ?

Zach Borboa

unread,
Dec 16, 2012, 1:53:43 PM12/16/12
to Sam Solomon, django-d...@googlegroups.com
> 1) Being able to create redirects (which seems to already be on the
> todo-list)

Creating temporary 302 redirects are currently possibly right now. The
TODO is for being able to specify both 301 and 302 redirects through
the admin.


> 2) Being able to specify extra kwargs to pass to a view so that it would be
> possible to change the functionality of a view without adding a new model to
> store the different options (or have to change the urlconfig and push new
> code every time).

You can still specify additional urls in urls.py as the framework
allows you to do normally; django-urls simply appends to that list of
urls. There is also a TODO for adding the ability to edit views
through the Django admin using the same editor GitHub uses. These
should cover the use cases you describe.


On Sat, Dec 15, 2012 at 11:52 PM, Sam Solomon <sss...@gmail.com> wrote:
> Yeah, I agree, as it is, I can't see any reason why I would use it, but I
> could see it being useful with some modifications such as:
>
> 1) Being able to create redirects (which seems to already be on the
> todo-list)
> 2) Being able to specify extra kwargs to pass to a view so that it would be
> possible to change the functionality of a view without adding a new model to
> store the different options (or have to change the urlconfig and push new
> code every time).
>
> Until those things are implemented (which allow for things that could
> probably be implemented in more straightforward/non-dev-user friendly ways),
> it seems like a bad idea to store infrastructure in the database (I can only
> see it causing problems when you have developers working from a different
> urlconf than the production server is using).

Tom Christie

unread,
Dec 16, 2012, 2:20:09 PM12/16/12
to django-d...@googlegroups.com, Sam Solomon
Since this isn't really appropriate for django-dev, could we move any further discussion on this over to the django-users group, please?

Many thanks!

  Tom
Reply all
Reply to author
Forward
0 new messages