This list is for discussion of the development of Django, not for
discussing uses of Django.
Also, generally it's a good idea to use Google to search for an answer
to questions like this.
--
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."
--
You received this mes
Hello everybody
i've a question. Have any free django hosting site ?
Kind Regards
Tsolmon
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this gr
On Jun 14, 10:59 am, Hooshyar wrote:
> Hello all,
>
> I am new to this group, although I am 4 years old with Django. I have
> a question. If this is not the right place, I apologize in advance.
> Please refer me to a proper mailing list. Please reply here or you can
> e-mail me directly, if you wi
On Tue, Jun 15, 2010 at 10:46 AM, George Sakkis wrote:
> ...In the current save_base()
> implementation, pre_save is sent before the instance's existence is
> determined, so I'm not sure if postponing it would break existing
> code. If there is no backwards compatibility issue, I can open a
> tick
On Jun 16, 8:01 am, Gustavo Narea wrote:
> Hello.
>
> Russell said:
>
>
>
>
>
> > > It should be easy, specially since you already use WSGI middleware in
> > > that server internally (i.e., the AdminMediaHandler).
>
> > > In runserver.py, you could replace:
> > > try:
> > > handler = A
On Jun 16, 8:11 am, Gustavo Narea wrote:
> Hello, Graham.
>
> Graham said:
>
> > From what I remember of this thread, haven't been following it too
> > closely though, I would think the idea of relying on WebOb and Paste
> > Deploy is a bad idea.
>
> > There are bigger issues around WSGI deploym
On Tue, Jun 15, 2010 at 5:23 AM, Jack Shedd wrote:
> Back during one the last Chicago bash, I coded up a fix for Ticket 2594,
> which would ensure template tags collapsed on themselves within the final
> source of a rendered template.
>
> http://code.djangoproject.com/ticket/2594
>
> Just wonder
On Wed, Jun 16, 2010 at 1:04 AM, Giuseppe Ciotta wrote:
> On Wed, Jun 16, 2010 at 12:46 AM, Jeremy Dunck wrote:
>> On Sun, Jun 13, 2010 at 7:18 AM, lenz wrote:
>>> Could you share your code with us?
>>> Thanks you!
>>
>> This might help:
>> http://gist.github.com/425403
>
> I have some similar c
On Wed, Jun 16, 2010 at 12:46 AM, Jeremy Dunck wrote:
> On Sun, Jun 13, 2010 at 7:18 AM, lenz wrote:
>> Could you share your code with us?
>> Thanks you!
>
> This might help:
> http://gist.github.com/425403
I have some similar code here: http://gist.github.com/439868
It might be better because
On Fri, Jun 11, 2010 at 1:43 PM, Jan Murre wrote:
> On Fri, Jun 11, 2010 at 3:13 PM, Tom Evans wrote:
>> On Fri, Jun 11, 2010 at 11:41 AM, jjmurre wrote:
>>> Hi,
>>>
>>> I am using long living session in the database backend. Because of
>>> Robots I am getting a huge amount of sessions. I google
On Sun, Jun 13, 2010 at 7:18 AM, lenz wrote:
> Could you share your code with us?
> Thanks you!
This might help:
http://gist.github.com/425403
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-dev
On 15/06/2010 20:52, Brian Luft wrote:
Short of new tutorials, I think the best service we could do for the
(beginner) community is to at least call out a sidebar that provides
some brief context around whether or not to namespace by project.
Since this is a matter of personal preference the res
Hello, Graham.
Graham said:
> From what I remember of this thread, haven't been following it too
> closely though, I would think the idea of relying on WebOb and Paste
> Deploy is a bad idea.
>
> There are bigger issues around WSGI deployment that need to be solved
> and using Paste Deploy as it
Hello.
Russell said:
> > It should be easy, specially since you already use WSGI middleware in
> > that server internally (i.e., the AdminMediaHandler).
> >
> > In runserver.py, you could replace:
> >try:
> >handler = AdminMediaHandler(WSGIHandler(), admin_media_path)
> >
> > with:
>
I would love to see the aggregate classes (Sum, Avg, etc) take an
optional second parameter that becomes the value in a coalesce
statement in the resulting query. Basically, this would function a
lot like dict.get. Right now the only option is to resolve to None.
If, for instance, you could say
This topic came up in discussion today and Peter pointed us here.
Kudos to Andrew for showing initiative.
Short of new tutorials, I think the best service we could do for the
(beginner) community is to at least call out a sidebar that provides
some brief context around whether or not to namespace
Another option that hasn't come up is to just have a custom __setattr__ that
won't let users write to self (therefore providing primitive thread safety).
I don't think it is a /good/ option, but I am just throwing it out there for
completeness.
_Nick_
On Tue, Jun 15, 2010 at 7:10 AM, Patryk Zaw
Apologies if this has come up before, I didn't find anything related
in the archives.
As Model.save() is called both for inserts and updates, it would
sometimes be useful for pre_save listeners to know whether the
instance exists or not. This information is sent with post_save but by
then it may b
On Tue, Jun 15, 2010 at 10:46 AM, Arthur Koziel wrote:
> 4. Also in the same changeset, the 'nesting_level' and 'can_postpone'
> variables were introduced. These fixed a problem where the package is still
> being imported by Python and the model module isn't available yet. Again, I
> couldn't repr
On Tue, Jun 15, 2010 at 9:46 AM, Arthur Koziel wrote:
> Hey there,
>
> I'm making some progress on the app loading gsoc project. I'm still in the
> process of writing tests for the AppCache. It took me longer than I've
> thought. However, I'm really confident that I'll finish the testing stuff
Hey there,
I'm making some progress on the app loading gsoc project. I'm still in the
process of writing tests for the AppCache. It took me longer than I've thought.
However, I'm really confident that I'll finish the testing stuff this week and
move on to writing the new App class. There are st
If you don't mind, I'll talk a bit more to myself.
On Tue, Jun 15, 2010 at 3:38 PM, Patryk Zawadzki wrote:
> I really don't think we should add anti-moron filters at the framework
> level past documenting "taking care to ensire immutability of view
> instances".
This came out a bit harsh. What I
After giving it more thought:
The supposed View class is a pure utility class that is close to a
module. It does not represent a state in an application, it takes
input and returns output, none of it should outlive a "__call__" call.
Therefore I see no reason for a proper implementation to not be
23 matches
Mail list logo
