If I run python manage.py runserver and try to access the page, it work right, with or without "import xmlrpclib"...humm...very stranger, maybe problem whit mod_python-3.1.4 or apache-2.0.53??
-- SDM - www.Garimpar.com/noticiashttp://sdm.zapto.org/--"Orientacao a Objeto sempre existiu, mas no
thank you guys for the response... I guess we will have to go back
using one-to-one till the inheritance is there...
best regards,
--FX
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post
Hi, when I try to import xmlrpclib in my view, I got '' (nothing) from
the request, like this
this not work:
---8<---
import xmlrpclib
def myfunc(request):
return HttpResponse(..)
--->8---
this work:
---8<---
#import
Adrian Holovaty wrote:
> Default values aren't created at the SQL level -- they're enforced at
> the Django DB-API level.
OK, I figured that out the meantime, but it doesn't work for the
BooleanField.
When I define the default value for my BooleanField to True and then
create an object this
On Sun, Apr 23, 2006 at 03:14:15PM -0500, Adrian Holovaty wrote:
> Default values aren't created at the SQL level -- they're enforced at
> the Django DB-API level.
I thought that was only enforced by the admin functionality and that
if I wanted a default value for my views I'd have to write it
On 4/22/06, Viktor <[EMAIL PROTECTED]> wrote:
> When I define a model:
>
> >>> class Test(models.Model):
> >>> ... some other fields ...
> >>>bool_field = models.BooleanField(default=True)
>
> Django generate next sql:
>
> CREATE TABLE `test_test` (
> `id` integer AUTO_INCREMENT
On 4/23/06, Lalo Martins <[EMAIL PROTECTED]> wrote:
> To the Django composers: can we pleeease have a real password field?
> And use that for User rather than all that contortion? It's of very
> limited usefulness to see the raw password in the admin, and it makes it
> impossible for a non-geek
On 4/22/06, Chris Moffitt <[EMAIL PROTECTED]> wrote:
> I was playing with a small app the other day (in m-r) & had trouble with
> one of my models showing up in the admin interface. After much scratching
> of my head, I found the I had written -
> supplier = models.ManytoManyField(Supplier)
>
>
Jan Claeys wrote:
> Op zo, 23-04-2006 te 18:37 +0200, schreef gabor:
>> so when one clicks on the logout link, it's simply not submitted.
> [...]
>> i don't know what's the correct behavior from the http point of view
>> (if a page does not specify any cache-setting, should it be cached or
>>
Op zo, 23-04-2006 te 18:37 +0200, schreef gabor:
> so when one clicks on the logout link, it's simply not submitted.
[...]
> i don't know what's the correct behavior from the http point of view
> (if a page does not specify any cache-setting, should it be cached or
> not),
A simple link, a HTTP
hi,
when using the django admin interface,
the logout does not work in opera.
after some investigation, i found the problem (and also the solution).
it seems that opera caches the pages quite aggressively..
by default, django-admin does not send any cache-headers.
so opera caches every
Ok, create_user is now User.object.create_user for those wondering.
To the Django composers: can we pleeease have a real password field?
And use that for User rather than all that contortion? It's of very
limited usefulness to see the raw password in the admin, and it makes it
impossible for a
12 matches
Mail list logo
