Re: Request for advice on refactoring a big Django project

2017-03-06 Thread Bob Haugen
Antonis, thank you very much for the feedback! You are absolutely correct! I apologize to you and the list, and will strive to follow your suggestions in the future. I suspect, however, that the very long explanation that would have been required to avoid the links would have been offputting, too.

Re: getting "DateTimeField received a naive datetime" error but have no DateTimeFields

2012-12-15 Thread Bob Haugen
ctive responding on django-users lately. On Sat, Dec 15, 2012 at 4:13 AM, Bob Haugen wrote: > On Sat, Dec 15, 2012 at 1:16 AM, Chris Cogdon wrote: >> I never got the warnings you got, but I got three errors along the lines of: >> IntegrityError: valueaccounting_economicagent.created_

Re: getting "DateTimeField received a naive datetime" error but have no DateTimeFields

2012-12-15 Thread Bob Haugen
On Sat, Dec 15, 2012 at 1:16 AM, Chris Cogdon wrote: > I never got the warnings you got, but I got three errors along the lines of: > IntegrityError: valueaccounting_economicagent.created_date may not be NULL > Want me to grab a different revision from git ? Fixed that one. You could do a git p

Re: getting "DateTimeField received a naive datetime" error but have no DateTimeFields

2012-12-14 Thread Bob Haugen
Also, I recognize this is way beyond the call of duty, but if you really want to reproduce the problem, you might need to follow: https://github.com/valnet/valuenetwork/blob/master/docs/install.txt On Fri, Dec 14, 2012 at 7:06 PM, Chris Cogdon wrote: > Checked out the code and attempted to run "m

Re: getting "DateTimeField received a naive datetime" error but have no DateTimeFields

2012-12-14 Thread Bob Haugen
I'm running ./manage.py test valueaccounting -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups

Re: getting "DateTimeField received a naive datetime" error but have no DateTimeFields

2012-12-14 Thread Bob Haugen
On Fri, Dec 14, 2012 at 6:07 PM, Chris Cogdon wrote: > Throw the code up somewhere I can see the results for myself? https://github.com/valnet/valuenetwork/blob/master/valuenetwork/valueaccounting/tests.py -- You received this message because you are subscribed to the Google Groups "Django use

Re: getting "DateTimeField received a naive datetime" error but have no DateTimeFields

2012-12-14 Thread Bob Haugen
But sincerely, Chris, thanks for hanging in there on this. I baffled. On Fri, Dec 14, 2012 at 5:51 PM, Bob Haugen wrote: > On Fri, Dec 14, 2012 at 5:42 PM, Chris Cogdon wrote: >> Okay, so when you create your datetimes, are you defining them with a >> timezone ? > > I tri

Re: getting "DateTimeField received a naive datetime" error but have no DateTimeFields

2012-12-14 Thread Bob Haugen
On Fri, Dec 14, 2012 at 5:42 PM, Chris Cogdon wrote: > Okay, so when you create your datetimes, are you defining them with a > timezone ? I tried that; did not make any difference. The error messages came up before any of the test setup code ran. (I put a pdb trace in at the start; the error me

Re: getting "DateTimeField received a naive datetime" error but have no DateTimeFields

2012-12-14 Thread Bob Haugen
On Fri, Dec 14, 2012 at 3:02 PM, Chris Cogdon wrote: > Nothing definitive, but from checking the location of the code that is > raising the warning, I suspect one of the following: > > 1. USE_TZ is not set in your production code, but _is_ set in your settings > file for your tests. Of course, you