In this mailing list alone, Michael, Tom, David, Felipe, julianb, Ian and I
have all proposed different solutions. 7 different solutions to what
appears to be a very common problem. :(
Tom:
As you said the get_instance_or_404 only works for simple cases.
The switcher view only works if the
Tom, you're right about the second and third points though. If the user
perform any operation with side effect that requires writing to the
database before the view checks whether the keyword arguments are
appropriate and decide to raise DoesNotResolve, it can definitely be a
source of
Hi Tom, interested to see why you think a single wrapping view is a
reasonable alternative for the example I showed above, where you have
following list of URLs:
// # front page for country
// / # list of schools and companies with activities in
that industry, in that country
/// # list of
I've just read the previous discussion and I now have the same conclusion
as yours - the optional request argument doesn't provide much the user
can't do easily anyway. They can always make a custom function to grab the
site based on the request.
The value of Site.objects.get_current() as you
Is the 'vote' a majority or a consensus must be achieved?
--
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.
Previous discussion (which I've read before):
https://code.djangoproject.com/ticket/16774
--
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
What action, if any, do you suggest I take now?
On Tuesday, March 26, 2013 2:42:11 PM UTC+11, Ramiro Morales wrote:
>
> On Tue, Mar 26, 2013 at 12:36 AM, meric <meri...@gmail.com >
> wrote:
> > Thanks, I'll reply to that thread. I posted my proposal 6 months before
>
I've previously raised this idea and created a pull request.
https://github.com/django/django/pull/378
The problem with creating with a catch all view:
You have following models:
Country, Industry, Company, School.
You want to have the following kinds of urls:
//
// /
///
///
/ /
Thanks, I'll reply to that thread. I posted my proposal 6 months before
that post, would've been nice if they posted in my thread...
On Tuesday, March 26, 2013 2:33:14 PM UTC+11, Ramiro Morales wrote:
>
> On Tue, Mar 26, 2013 at 12:28 AM, meric <meri...@gmail.com >
> wrote:
I have made a pull request for django 6 months ago, but it doesn't seem to
be getting much response so far.
What can I do to get more feedback as to what's wrong with it, and try to
get it accepted?
Here is the pull request:
https://github.com/django/django/pull/378
--
You received this
Previous discussion:
https://groups.google.com/forum/?fromgroups=#!searchin/django-developers/dynamic$20sites/django-developers/QSXLGSxy7Vk/TxgiJzz5nd8J
https://code.djangoproject.com/ticket/16983
https://code.djangoproject.com/ticket/4438
My proposal allows getting the current site based on
The ticket page is here: https://code.djangoproject.com/ticket/16774
I previously said people trying to resolve URLs in their code may have
difficulty because the DoesNotResolve exception is not raised until the
view is run. Just now I thought how it would be done. I think changing
Hi,
I looked at https://code.djangoproject.com/ticket/16774 and decided to
implement the feature where views can raise urlresolvers.DoesNotResolve to
make URL Resolver to keep searching for a URL.
The diff is here: https://github.com/meric/django/compare/ticket_16774
It introduces a new
13 matches
Mail list logo
