2008-5-31
| 02:36 | vomjom | using the latest SVN for both django and django_sqlalchemy with a DateTimeField in a model, i get: |
| 02:37 | vomjom | File "/usr/local/lib/python2.5/site-packages/django_sqlalchemy/models/fields/__init__.py", line 82, in sa_column_kwargs |
| 02:37 | vomjom | kwargs = dict(onupdate=self.onupdate) |
| 02:37 | vomjom | AttributeError: 'DateTimeField' object has no attribute 'onupdate' |
| 02:39 | empty | vomjom: this is the latest, as of a day or so ago? |
| 02:39 | vomjom | just checked out about 5 mins ago |
| 02:40 | empty | vomjom: okay, well there's kinks to work out on that but I wanted to get it merged as the changes were huge. So let me dig into it. |
| 02:40 | vomjom | thanks :) |
| 02:41 | empty | vomjom: would you http://dpaste.com/ your model |
| 02:42 | vomjom | okay, but i need to single it out first because i have a couple that could be culprits |
| 02:42 | empty | you know what, why don't you wait. |
| 02:42 | empty | I think I have an idea. |
| 02:44 | vomjom | hmm |
| 02:45 | vomjom | fyi i commented out all the models and it gave me that same error :P, but the apps that come with django_sqlalchemy in the tests directory seem to work |
| 02:46 | empty | vomjom: have you deleted pyc? |
| 02:46 | empty | there was quite a bit of changes. |
| 02:46 | empty | also here's another thing. |
| 02:46 | empty | is it when you're just going into the shell? |
| 02:46 | empty | or is it when you're doing a save |
| 02:46 | vomjom | shell |
| 02:46 | vomjom | empty, this is a first install of django_sqlalchemy so i don't think .pyc would be the problem |
| 02:47 | vomjom | i guess i'll try it, though |
| 02:47 | empty | oh okay |
| 02:47 | empty | do you have a DateField or a DateTimeField in your model? |
| 02:47 | vomjom | empty, when i commented out the models, it gave me the same error |
| 02:47 | vomjom | i'm wondering if it's user error :P |
| 02:47 | vomjom | i'll try to dig into the problem further |
| 02:47 | empty | okay, because I just added a DateField with onupdate and it works. |
| 02:48 | empty | and one without and it works. |
| 02:48 | empty | but it definitely could be a problem with dj-sa because like i said, huge changes. |
| 02:49 | vomjom | apparently it's django.contrib.auth that's giving me the issue |
| 02:49 | empty | oh well that could be. |
| 02:49 | empty | honestly I haven' t started testing third party stuff now. I just got class replacement working. |
| 02:50 | vomjom | ah, okay |
| 02:50 | empty | That's sort of my next step |
| 02:50 | empty | Maybe I'll start with auth |
| 02:50 | empty | just to see |
| 02:52 | empty | vomjom: yep it's auth |
| 02:55 | brosner | did i hear class replacement is working? |
| 02:57 | empty | sorta |
| 02:57 | empty | nah, it is |
| 02:57 | empty | but I just committed it finally. I have a lot more testing to do |
| 02:57 | brosner | kick ass empty :) |
| 02:57 | empty | and parts are a bit hackish, but I plan to clean that up. |
| 02:57 | empty | brosner: yeah it's pretty cool. Now on to testing third party stuff. :) |
| 03:16 | empty | vomjom: grab the latest. It should at least not error now. Beyond that I'm not sure. I'll test it over the next couple of days to see how far I get. |