On 6/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I'll start working in that direction tomorrow, if that seems like a
> good plan. I'm going to be mostly internetless for the next 2 weeks or
> so, so it will be a while before I can actually submit a patch that's
> fully functional. But I
On 6/6/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I like this one. I would prefer to see the error is thrown whenever we
> are going to add a slash and the method is POST. Checking for POST data
> is probably over-specialising. The problem we are trying to solve is
> User Agents
You could also use Tidy, there's a couple python wrappers for it:
TidyLib wrapper: http://utidylib.berlios.de/
Classic Tidy: http://www.egenix.com/files/python/mxTidy.html
Which should work on all platforms and can even be used to correct
the page before outputting it.
On 08/06/2006, at 1:00
Luke Plant wrote:
> I'm not sure how useful it is for Mac and Windows users. The middleware
> doesn't actually do any validation -- it's done by 'validate' from
> Debian's 'wdg-html-validator'. I personally wrap that in a shell
> script which beeps and pops up a KDE notification when a page
> As I mentioned in another note to this thread, things are the way they
> are because I didn't want to load all the rarely-used reflection stuff
> into memory each time a model is used. That said, if it helps your
> goal (which would be a great Django addition), let's go ahead and make
> those
> And, in any case, they need to know the table name (and quite
> possibly database name and connection proxy) for the related tables. So
> you are going to have do a pass through all the models and build up the
> graph of dependencies and make that available to each model at
> construction time
On 6/8/06, Jure Èuhalev <[EMAIL PROTECTED]> wrote:
>
> I would like implement interactive file upload progress using AJAX.
> I'm already using patch from ticket #1484 to make large uploads
> possible.
>
> I would be interested in any hints how could I follow the upload
> session of a user (as far
I would like implement interactive file upload progress using AJAX.
I'm already using patch from ticket #1484 to make large uploads
possible.
I would be interested in any hints how could I follow the upload
session of a user (as far as I understand view function gets called
only after POST is
On 6/7/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> I'm not sure how useful it is for Mac and Windows users. The middleware
> doesn't actually do any validation -- it's done by 'validate' from
> Debian's 'wdg-html-validator'. I personally wrap that in a shell
> script which beeps and pops up a
I first posted this on the Django userslist but got no response, maybe
some on this list knows an answer.
Hi,
I wonder what's the preferred way/best practice for sanitizing user
input. Most fields of my models are not allowed to contain HTML tags or
javascript. I could use the striptags filter
On Wednesday 07 June 2006 15:49, Adrian Holovaty wrote:
> Should we add the HTML-validation middleware to Django contrib? Luke,
> would you be interersted in that?
I would be fine with that -- it's nice to have something to give back,
and if it raises the standard of Django apps being released
On 6/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I'd argue that the right solution here would be to push the brains
> farther out to the edge. Have management functions call class methods
> on models to execute table creation, initial data loading, etc, rather
> than having them poll the
On Wed, 2006-06-07 at 22:25 +, [EMAIL PROTECTED] wrote:
[...]
> However, I've run into a problem that can't be fixed with little
> patches, in django.core.management. Specifically, all of the many
> get_sql_* functions in there pull together sql from multiple models and
> execute it all with
On 6/7/06, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
> On 6/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > I'd argue that the right solution here would be to push the brains
> > farther out to the edge. Have management functions call class methods
> > on models to execute table creation,
On 6/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I'd argue that the right solution here would be to push the brains
> farther out to the edge. Have management functions call class methods
> on models to execute table creation, initial data loading, etc, rather
> than having them poll the
I've been hacking away today at a patch for #1142 (multiple database
connection support), which is the last serious technical hurdle to my
company's use of django -- a very itchy itch for me to scratch.
Mostly things have gone well. My basic design is to add, as a
supplement to the current
On 6/7/06, Steven Armstrong <[EMAIL PROTECTED]> wrote:
...
> GET /some/url/?cm_data_id=78fsd8fasdf7ad8asaf7889sdf
>
> - load POST/GET data from /tmp/78fsd8fasdf7ad8asaf7889sdf, populate
> POST/GET dicts with it
> - remove cm_data_id from GET variables
> - delete /tmp/78fsd8fasdf7ad8asaf7889sdf
>
On 06/07/06 05:11, Adrian Holovaty wrote:
> http://code.djangoproject.com/wiki/NewbieMistakes#POSTtoviewslosesPOSTdata
>
> It's about time to solve this one. Who has a creative, elegant solution? :-)
>
> Some ideas, just to start discussion --
>
> * THROW ERROR ON POST: The CommonMiddleware,
Is there a reason _request_middleware's are called in the BaseHandler,
while _response_middleware's are called in the subclass (i.e.
ModPythonHandler)?
Also, in BaseHandler.load_middleware, I noticed that an exception
loading any middleware will leave the middlewares not None, but also
not valid
On 6/7/06, gabor <[EMAIL PROTECTED]> wrote:
> so now the decisions are already done, and when all the fields will have
> the necessare to_python (+validate) methods, then save will be changed
> to call validate, and the task is done?
>
> or still some decisions have to be done first?
>
> i'm
hi,
after i spent some painful time with the AddManipulator in a non-web
python script :-), i went to check the status of the validation-aware
models.
seems the last checkin was http://code.djangoproject.com/changeset/2518.
so now the decisions are already done, and when all the fields will
This post on django-users:
http://groups.google.com/group/django-users/msg/7d4773cccde8d51d
manifests some interest in moving the old-style classes to new-style:
with some fairly short grunt work I made a patch about it, and attached
it to ticket #2109:
On 7 Jun 2006, at 16:23, Jeremy Dunck wrote:
> Hmm, this sort of thing suggests that "email when bad stuff happens"
> would be a nice general feature.
... or a general logging feature (with the ability to send email as
one of the log actions).
Hey Adrian,
Adrian Holovaty wrote:
> Michael, you have stumbled upon an idea that I've coincidentally also
> wanted to do since before Django was open-sourced! See
Very Nice ;-)
But have you checked how I'm doing this different?
- Since data that does not pass tese "advisory tests" can get
On 6/7/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> I already wrote a validator app that checks
> outgoing HTML for validity, using a middleware to intercept the
> response. It also stores all details of failed pages so you can go
> back to them, which would be overkill in this case.
Hmm, this
On 6/7/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> My pleasure. I've updated it for magic-removal (and that version is
> uploaded to my bzr repos), but I need to package it up and release it
> properly. When I finally get time to do that I'll post a blog about it
> or something.
Should we add
On 6/7/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Now, is there interest in having such a thing in Django? Currently, I try to
> keep the
> patching minimal, but I don't see how I could avoid it. If this would go into
> Django
> eventually, it could be solved cleaner and easier. For
Hi,
I currently find myself needing something very similar to the validation
framework. It's best explained with an example:
There is a form that configures email forwarding. The form will not only
validate well-formedness of the target addresses, but it will also check
whether its domain
Is there anyway to add a voting module to trac? A recent thread
discussed ways to improve the dev process, and I think something as
simple as a voting module could help quite a bit. The basic problem
I'm trying to address is the divide between what users and developers
feel are important. This
Malcolm Tredinnick wrote:
> Not entirely on-topic, but I must say that I think your HTML validation
> middleware deserves to be much better known. I was using it last week to
> check out some pages prior to release. It's very handy in development.
>
> Thanks. :-)
My pleasure. I've updated it
Malcolm Tredinnick wrote:
> Michael,
>
> On Wed, 2006-06-07 at 11:11 +0200, Michael Radziej wrote:
>> Hi,
>>
>> is this again just me :-), or has some checkin changed an error message
>> recently?
>> If I run the test suite, I get:
>>
>> 'invalid_models' module: Validator found 47 validation
On Wed, 2006-06-07 at 02:12 -0700, Luke Plant wrote:
>
> Simon Willison wrote:
>
> > It's certainly a nasty solution here, but we shouldn't rule
> > inspecting generated pages for errors out completely - just as long
> > as anything like that is hived off in to a specialist tool.
>
> You could
Michael,
On Wed, 2006-06-07 at 11:11 +0200, Michael Radziej wrote:
> Hi,
>
> is this again just me :-), or has some checkin changed an error message
> recently?
> If I run the test suite, I get:
>
> 'invalid_models' module: Validator found 47 validation errors, 47 expected
>
Simon Willison wrote:
> It's certainly a nasty solution here, but we shouldn't rule
> inspecting generated pages for errors out completely - just as long
> as anything like that is hived off in to a specialist tool.
You could do this pretty easily as a 'debug' middleware that is enabled
by
Hi,
is this again just me :-), or has some checkin changed an error message
recently?
If I run the test suite, I get:
'invalid_models' module: Validator found 47 validation errors, 47 expected
==
Missing errors:
On 7 Jun 2006, at 04:11, Adrian Holovaty wrote:
> * THROW ERROR ON FORM DISPLAY: If the APPEND_SLASH setting is set to
> True and the CommonMiddleware is activated, Django could check the
> output of every page for a whose method is POST and has an
> "action" whose URL doesn't end in a slash.
36 matches
Mail list logo
