Thanks Aymeric, I've reopened the ticket. I skipped the triage page,
thinking it would be about the rules for prioritizing bugs.
On May 15, 3:44 pm, Aymeric Augustin
wrote:
> Hello,
>
> On 15 mai 2012, at 21:36, Yo-Yo Ma wrote:
>
> > I've attached a diff in the ticket I created, and I resolved th
Hello,
On 15 mai 2012, at 21:36, Yo-Yo Ma wrote:
> I've attached a diff in the ticket I created, and I resolved the
> ticket as "fixed" (as habit, I'm used to doing this for work, allowing
> QA to change the status to "closed" after testing). Is this correct?
We resolve tickets as "fixed" only on
I've attached a diff in the ticket I created, and I resolved the
ticket as "fixed" (as habit, I'm used to doing this for work, allowing
QA to change the status to "closed" after testing). Is this correct?
Also, is it better to fork Django and make a pull request on GitHub,
or simply provide the git
I've just created https://code.djangoproject.com/ticket/18314 and
intend to take a look a better into the implementation of
``build_absolute_uri()`` tonight.
On May 13, 10:02 pm, Russell Keith-Magee
wrote:
> Thanks for the report -- but is there a particular reason that you're
> reporting this he
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
>
> leads to request.build_abs
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 django-develope
