I have found from where was the error coming.
More details on http://code.djangoproject.com/ticket/3973.
Thanks
Baptiste
On 8 avr, 19:07, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
> On 4/7/07, Baptiste <[EMAIL PROTECTED]> wrote:
>
> > I don't know how that was before, but with your commits of
Hi,
On 4/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
>
> * The name "values" is a bit too abstract -- it took me a while to
> figure out exactly what this framework *does*. Maybe something like
> "editable constants" or "model-specific options" would be more clear.
Isn't a constant supposed
Why has django not a interactive AJAX traceback debugger?
Using a interactive debugger you can play with objects at any point in
the error traceback.
I known, a web shell is a open security hole. But the interactive
debugger should only running with the development Web server and if
debugging is
Hi,
On Mon, 2007-04-09 at 04:33 -0700, jedie wrote:
> Why has django not a interactive AJAX traceback debugger?
>
> Using a interactive debugger you can play with objects at any point in
> the error traceback.
>
> I known, a web shell is a open security hole. But the interactive
> debugger shou
On 4/9/07, Marc Fargas Esteve <[EMAIL PROTECTED]> wrote:
> Hi,
>
> On 4/8/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> > * The name "values" is a bit too abstract -- it took me a while to
> > figure out exactly what this framework *does*. Maybe something like
> > "editable constants" or "model-
Hi,
On Apr 9, 1:48 pm, Malcolm Tredinnick <[EMAIL PROTECTED]>
wrote:
> Instead, it is triggered by whether or not DEBUG is True. Sometimes you
> want to have DEBUG=True in production environments, whether for just a
> little period of time -- to debug something -- or for longer. So I am
> relucta
If the only concern here is that debugging is a powerful feature that
needs to be carefully controlled, then surely a setting to enable it is
the right way to go? After all, many security experts will tell you
that the traceback handler we have now is a security hole, not because
it lets you e
On Apr 8, 11:18 pm, "oggie rob" <[EMAIL PROTECTED]> wrote:
> So, my first question is whether this could be designed to work
> without respect to models. For example, there are a lot of cases where
> views might refer to the same data, but not the same models. It would
> seem cleaner if there were
Hi,
I found an official web service from the european union to validate VAT
registration numbers using SOAP.
I will have to use that for my projects but I'd like to share it with
Django community.
At this time I just started to play with it but I wanted to discuss how
to integrate that and w
I've made this snippet: http://www.djangosnippets.org/snippets/164/
that I strongly believe should be part of Django (with little
polishing of course).
If newforms admin started to use that, we could give all views an
ability to use fieldsets too. That could be inserted to same file as
BaseForm o
Hi,
Can you provide an URL for those who haven't found such service? (The
spanish site for checking VAT's is like... s**t)
Maybe the best place to hold this is on it's own project (code.google.com?)
as a standalone application that users can checkout and put in
INSTALLED_APPS. And when it fine and
Hi,
> Can you provide an URL for those who haven't found such service? (The
> spanish site for checking VAT's is like... s**t)
Question 16 in VIES faq has a link to WSDL file:
http://ec.europa.eu/taxation_customs/vies/en/faqvies.htm#item16
There is also a form that can be used for manuel quer
Hello everyone!
Malcolm has introduced DATABASE_CHARSET in changeset 4971[1] in a
unicode branch. If I remember correctly this setting was needed if we
have out internals in byte strings. But if internals are in unicode we
(theoretically) can feed them as utf-8 or even in pure unicode to a
da
As implemented now in unicode branch templates are loaded from files
stored only in utf-8 (as far as I can read the code). However there's a
problem with legacy template files that are stored in one-byte
encodings. This is unfortunately not a rare thing and happen to raise
offenses from develo
On Apr 9, 9:02 am, "Gulopine" <[EMAIL PROTECTED]> wrote:
> > So, my first question is whether this could be designed to work
> > without respect to models. For example, there are a lot of cases where
> > views might refer to the same data, but not the same models. It would
> > seem cleaner if ther
There is a problem with:
http://code.djangoproject.com/ticket/3247
http://groups.google.com/group/django-developers/browse_thread/thread/50150b61aca46a7e
I've made a first working version but my implementation reverses the
changes described in the above ticket/discussion. Here's a summary of
wha
I've uploaded the code to my website.
http://jeroen.concept-q.com/projects/djangoalchemy/
(I'm sorry to admit that the website is plain unworkable in IE6, and
slow in other browsers. My use of transparency proves a tad ambitious)
--~--~-~--~~~---~--~~
You receive
Hoi,
Alright. Patch here: http://pocoo.org/~mitsuhiko/django_debugger.patch
Screenshot here: http://pocoo.org/~mitsuhiko/djangodebug.png
(Note, I edited those files in the same checkout I did the patches for
the __loader__ hook. So the patch is a bit bigger. Sorry for that)
Enable by adding ENA
I found a variable in django/core/management.py file named
project_name, its content should be the project name but it's not. It
saves the parent directory name instead, so I wrote a patch that fix
it.
Please, see
http://code.djangoproject.com/ticket/3846
Regards!
--
http://www.advogato.org/p
On 4/9/07, Mario Gonzalez <[EMAIL PROTECTED]> wrote:
> I found a variable in django/core/management.py file named
> project_name, its content should be the project name but it's not. It
> saves the parent directory name instead, so I wrote a patch that fix
> it.
>
> Please, see
> http://code.dja
On Apr 9, 4:58 pm, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote:
>
> Thanks, Mario. I've checked in the patch.
>
ok, I hope it help. Thanks for your time, regards!
>
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Ivan,
On Mon, 2007-04-09 at 18:35 +0400, Ivan Sagalaev wrote:
> Hello everyone!
>
> Malcolm has introduced DATABASE_CHARSET in changeset 4971[1] in a
> unicode branch. If I remember correctly this setting was needed if we
> have out internals in byte strings. But if internals are in unicode we
On Mon, 2007-04-09 at 18:56 +0400, Ivan Sagalaev wrote:
> As implemented now in unicode branch templates are loaded from files
> stored only in utf-8 (as far as I can read the code). However there's a
> problem with legacy template files that are stored in one-byte
> encodings. This is unfortun
On Mon, 2007-04-09 at 18:28 +, [EMAIL PROTECTED] wrote:
>
> There is a problem with:
> http://code.djangoproject.com/ticket/3247
> http://groups.google.com/group/django-developers/browse_thread/thread/50150b61aca46a7e
>
> I've made a first working version but my implementation reverses the
>
http://code.djangoproject.com/ticket/2884
this ticket was opened 6 months ago with a patch, fixing a bug where a
ProgrammingError is raised when sorting by a foreign key field which
has an ordering clause that contains further foreign key fields.
i ran into this bug when specifying a foreign key
Malcolm Tredinnick wrote:
> The only reference to DATABASE_CHARSET in that changeset was an
> accidental leftover in the postgresql (psycopg1) backend. That was an
> error. I removed it in r4972. :-)
Great!
--~--~-~--~~~---~--~~
You received this message because y
Malcolm Tredinnick wrote:
> I'm not so much worried about the one-off conversion (after all, it's
> for those peoples' benefit that we're doing this) as much as filesystems
> that store in a particular encoding by default. There's no reliable,
> non-expensive way to automatically detect the file
Hi all,
I'm trying to tie up the loose ends of the auto_now/auto_now_add
discussion so that I can bang together a patch.
auto_now_add can be pretty much replaced with default=datetime.now.
Honza raised the issue that the two aren't completely identical
because if you supply a value for the field
Malcolm Tredinnick wrote:
> On Mon, 2007-04-09 at 18:56 +0400, Ivan Sagalaev wrote:
>> As implemented now in unicode branch templates are loaded from files
>> stored only in utf-8 (as far as I can read the code). However there's a
>> problem with legacy template files that are stored in one-byte
29 matches
Mail list logo
