Hi everyone, at DAO Maker (a cryptocurrency incubator company) we are
looking for a full time remote (with the option to work in our offices in
Prague) Python/Django back-end developer with 3+ years experience and
passionate about writing fast, efficient software in Python.
Please read the job
I had a similar issue, solved with a trick.
Try to explicit a save() method for your SuperDelegate this way:
def save(self, *args, **kwargs):
super(SuperDelegate, self).save(*args, **kwargs)
Giovanni
On 6 Set, 12:09, "[EMAIL PROTECTED]"
<[EMAIL PROTECTED]> wrote:
> A foreignkey in a
Hello,
I wrote a custom field and I would like to have a proper widget in
admin.
As you may guess reading my code I would like to manage that field
with a multiselect, but instead I get a regular select in admin. How
should I do it?
(relevant part should be definition of formfield)
#
Hi all,
I'm writing a custom field wishing to implement something similar to a
multiplechoice.
The problem is that when I run syncdb I receive a
AttributeError: 'ListField' object has no attribute 'db_column'
Any idea?
my models.py is:
-
I solved this.
It seems my models.py was wrong, I got a few FloatField without
max_digits and decimal_places set (it was coming from a 0.97pre
project).
On a remote Apache server I wasn't seeing the nice complaints that
normally Django dev-server shouts.
On 10 Ott, 18:48, Gio <[EMAIL P
t;[EMAIL PROTECTED]>
wrote:
> Are you sure that articolo is not None or that c is not an int or
> None?
>
> On Oct 10, 12:48 pm, Gio <[EMAIL PROTECTED]> wrote:
>
> > I get this error:
> > unsupported operand type(s) for +: 'NoneType' and 'int'
I get this error:
unsupported operand type(s) for +: 'NoneType' and 'int'
referred to this snippet of code, debug informations are pointing to
the line where the ChangeManipulator is:
-
articolo = Articolo.objects.get(codice = c)
try:
Yes, you are right.
Removing core=True solved the issue.
However I think an error message from admin web interface is needed
when things go wrong.
Or should the default model validator to point to the error?
As during all my experiments in the terminal where the server was
running I always got:
-
Let me add that it isn't a Python version problem, it's the same with
python 2.4 and 2.5.
Giovanni.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-
;
> Malcolm is right on this one; you need to figure out exactly what is
> going on before you submit a bug, because otherwise you are just
> wasting the programmers' time trying to reproduce the problem. Let's
> exhaust all the other possibilities first and figure
> The usual process when you have one version of code that is working and
> a more complicated version that is not working is to add features to the
> working version, one at a time, until it stops working. In that way you
> will be able to narrow down exactly which is the problematic step and
>
db again. Sometimes when working
> within the same class the syncdb doesn't change the database all the
> way (and rightly so). Give that a try and if it still doesn't work
> we'll try a different solution.
>
> On May 31, 1:03 pm, Gio <[EMAIL PROTECTED]> wrot
cond cheese topping.
>
> Thanks Nis and good luck Giovanni.
>
> Mn
>
> On May 31, 12:21 pm, Nis Jorgensen <[EMAIL PROTECTED]> wrote:
>
> > Gio wrote:
> > > Hi,
> > > I searched about this subject and found only a few very old posts, so
> > >
Hi,
I searched about this subject and found only a few very old posts, so
maybe there is a better solution now.
As you may guess the model I'd like to code is similar to the Pizza -
Toppings you know from the "Creating Models" documentation:
class Topping(models.Model):
# ...
class Pizza(mo
14 matches
Mail list logo
