My only concern with this is the thing with the usernames, whereby some
people don't use the same username on Trac as on GitHub, and that accounts
are automatically munged together if they have the same username.
As a demonstration, I found someone with the core developer tag on Trac
(lukeplant) w
+1 from me too - I've only tried using django.contrib.comments once, and it
ended up not being what I needed anyway, so I had to write my own comments
module (Disqus was out of the question)
On Thu, Mar 7, 2013 at 5:11 PM, Carlos Aguilar wrote:
> I think i can maintain comments if you want the t
Hey!
I'm in a similar boat to you, but this mailing list is for the development
of Django only, and not for general Django related questions.
You might want to try asking on the django-users list.
Luke
On Fri, Feb 8, 2013 at 12:07 PM, Kaung Htet Zaw wrote:
> Hi all,
>
> I am a teenager who h
ut.
> extra] don't silently continue when the url's first param fails to
> evaluate properly only to fail 3 lines later with an incomprehensible
> error message.
>
That smells like it should be filed as a bug to me.
Regards,
Luke Granger-Brown
--
You received thi
I think it would be good to make a new documentation page suggesting
various best practices - speaking from my point of view, it was hard for me
to figure out what I *should* be doing, because everyone was doing it
differently and each method had their own pros and cons. I ended up using a
mishmash
On Jul 3, 2012 1:59 PM, "Chris Wilson" wrote:
>
> Hi Reinout,
>
>
> On Tue, 3 Jul 2012, Reinout van Rees wrote:
>
>> On 30-06-12 16:22, Luke Plant wrote:
>>>
>>> Also, in Django to date we've eschewed external dependencies. That has
>>> been partly due to the poor and confusing state of Python pac
On Wed, Apr 18, 2012 at 11:55 PM, Dalton Barreto wrote:
> Em 18 de abril de 2012 19:46, Dalton Barreto
> escreveu:
> > Em 18 de abril de 2012 18:44, philipn escreveu:
>
> Hmm, this would probably disable pull requests too. Not a good idea,
> assuming that
> contributions will be accepted as pul
Can someone please review https://code.djangoproject.com/ticket/17627 for
me? I think I've resolved all the outstanding issues in my latest version
of the patch.
Regards,
Luke Granger-Brown
--
You received this message because you are subscribed to the Google Groups
"Django develop
+1 from me too - I've used {# #} across line boundaries before and wondered
why it didn't work, since it didn't seem especially clear that this doesn't
work nor why it doesn't work - I'd just substituted for the
obvious and eventually just deleted the offending HTML.
On Feb 24, 2012 9:30 AM, "Chri
> >
> > Obviously, this function cannot change in behaviour or name, so I
> > suggest altering the docs, dropping the clause about indicating that
> > the user has provided username and password to make it clearer what
> > this method does.
>
> It does prove that they've authenticated, in that requ
On Feb 23, 2012 3:41 PM, "Tom Evans" wrote:
>
> Hi all
>
> I don't like this function that much. It doesn't actually check
> whether users are authenticated - which is to say, they have presented
> credentials which we have accepted and authorized them to use to the
> site. Instead it always retur
On Feb 10, 2012 3:47 PM, "Adam "Cezar" Jenkins"
wrote:
>
> On Fri, Feb 10, 2012 at 9:50 AM, Carl Meyer wrote:
>>
>> "import .module"
>
>
> Not arguing one way or another, but the above has always worked for me
from a Python standpoint.
It shouldn't work - the Python 2.7.2 documentation says that
12 matches
Mail list logo
