This seems applicable to dcramer's django-db-log.
http://github.com/dcramer/django-db-log
This might also dovetail with logging support which may make it into
1.3, so it might be worth looping in the folks involved in that.
-justin
--
You received this message because you are subscribed to th
On Sep 8, 1:27 pm, Anssi Kaariainen wrote:
> > This is a real special case. ATM the formwizard isn't able to store invalid
> > forms. But if you are at the sprints in Portland, I would be happy to talk
> > to you about possible solutions.
>
> > Do you have any idea how this could be solved? (ma
On 2010-09-08, at 8:29 PM, David P. Novakovic wrote:
> Hey dude,
>
> What about something like sentry or lumberjack?
Or Arecibo. There's quite a few solutions to this that don't involve sending
email. In fact I use the django taking down your email server as an example for
Arecibo all the time
Hey dude,
What about something like sentry or lumberjack?
I haven't looked at them too seriously, but I'd imagine there'd be a
way to do smarter summarizing of emails etc..?
D
On Thu, Sep 9, 2010 at 1:26 PM, Simon Litchfield wrote:
> Hi all
>
> Default behaviour of sending an email on 500 erro
Hi all
Default behaviour of sending an email on 500 error is great.
Problem is on high traffic sites, and you might just be making a quick
update- literally within seconds you can bring your mail server down-
crash your mail client- or render your gmail account useless.
With "batteries included"
The Django team has just issued Django 1.2.2 to deal with a reported
security issue. Full details are available in the blog post:
http://www.djangoproject.com/weblog/2010/sep/08/security-release/
All users of Django 1.2 are urged to upgrade immediately.
--
"Bureaucrat Conrad, you are technicall
Amazingly accurate.
J. Leclanche
On Wed, Sep 8, 2010 at 9:24 PM, Jeremy Dunck wrote:
> http://www.scribd.com/doc/37113340/Why-Django-Sucks-and-How-we-Can-Fix-it
>
> Presented here without comment, except that video of will be available
> (probably on blip.tv) in (hopefully) a few weeks.
>
> -
On Sep 8, 7:47 pm, Stephan Jäkel wrote:
> Hi Scot,
>
> shacker wrote:
> > Not all forms are completed in a single sitting. We have a form with
> > more than 100 fields, which takes at least two hours for the user to
> > complete. Therefore it's essential that the (authenticated) user be
> > able t
http://www.scribd.com/doc/37113340/Why-Django-Sucks-and-How-we-Can-Fix-it
Presented here without comment, except that video of will be available
(probably on blip.tv) in (hopefully) a few weeks.
--
You received this message because you are subscribed to the Google Groups
"Django developers" gro
Hi Scot,
shacker wrote:
Not all forms are completed in a single sitting. We have a form with
more than 100 fields, which takes at least two hours for the user to
complete. Therefore it's essential that the (authenticated) user be
able to save it and return later to edit or complete it. IOTW ther
On Wed, 2010-09-08 at 10:22 +0200, Patryk Zawadzki wrote:
> Again, it's not there to counter attacks. Think of it as the
> equivalent of the "csrftoken" cookie which could be read in the exact
> same way. I just wanted a couple of strings that are not likely to
> change between form generation and
On 7 Sep 2010, at 16:48, David Reynolds wrote:
> Hi folks,
>
> I am running into a validation problem with ModelForms - here is a quick
> summary of what is happening
I have opened a ticket to track this
[http://code.djangoproject.com/ticket/14234]. I'd be happy to work up a patch,
but woul
> On Tue, Sep 7, 2010 at 10:04 PM, Luke Plant wrote:
>> Your method is quite flawed:
Just to make sure we're on the same side -- I'm not trying to make
_CSRF_ more secure (as there's not much more we can do here).
I'm trying to:
* make it work without resorting to Referer checks
* make it not u
On Tue, Sep 7, 2010 at 10:04 PM, Luke Plant wrote:
> On Mon, 2010-09-06 at 22:39 +0200, Patryk Zawadzki wrote:
>> Another approach would be not to use a cookie at all. For each {%
>> csrf_token %} use a slightly modified variant of the above
>> encode_cookie function with:
>>
>> values = {
>>
May I humbly suggest using IronPython as a first baby step?
It has the same syntax as CPython 2.6/2.7, but ALL text strings are in
unicode, just like in Python 3.x. 8-bit byte arrays must be declared
as such. I suspect that about half of the problems with Python 3
conversion will be in that very a
On Sep 7, 6:00 pm, Stephan Jäkel wrote:
> Hi,
>
> about 4 months ago, I started this thread. I want to give some news on
> django-formwizard to keep you all up2date.
Great to hear this is being worked on. At the djangocon forms session
today, I raised the following question and didn't get any con
16 matches
Mail list logo
