Thanks for the report -- but is there a particular reason that you're
reporting this here, rather than on the ticket tracker?
Yours,
Russ Magee %-)
On Mon, May 14, 2012 at 9:55 AM, Yo-Yo Ma wrote:
> A request to:
>
> http://www.example.com:8080//foo-bar-baz.html
>
>
A request to:
http://www.example.com:8080//foo-bar-baz.html
leads to request.build_absolute_uri() returning:
http://foo-bar.html
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to
That looks a lot like 15863.
https://code.djangoproject.com/ticket/15863
Which cache backend are you using? Which session backend? Are you
absolutely positive you are using Django 1.4, and not a
system-installed version of 1.3? Does your code pickle or unpickle
sessions or cookies anywhere
It would not be a "hard link". Do you know the definition of
"dependency graph", and do you know anything about Django's internals
or about how Django already allows you to connect models' foreign keys
this way? It would be simply "get me the model 'MyModel' from the app
'my_app'". The app could
Hi,
On Sun, May 13, 2012 at 3:08 PM, Shai Berger wrote:
> Hi,
>
> In the process of upgrading to Django 1.4, I've run into a little problem: one
> of our files uses django.contrib.auth.models.get_hexdigest, which is no longer
> present.
>
> I searched, and could find no
Hi,
In the process of upgrading to Django 1.4, I've run into a little problem: one
of our files uses django.contrib.auth.models.get_hexdigest, which is no longer
present.
I searched, and could find no mention of this in release notes, tickets, or the
developers group.
Was this, for some