the import should be fine, it's actually accessing the setting attributes that will cause import problems
same with that line, since it has the lambda:
frege
ahhhhhhhhhhhhhhhhhhhhhhhhhhhh
yeah I do this; os.environ.setdefault('DJANGO_SETTINGS_MODULE', '%s.settings' % settings.APP_NAME)
now it's working fine
asksol
ah, that would be a problem :)
frege
thanks asksol
was driving me nutz
:)
codeBandit has quit
asksol
should be added to the docs, several people has been evaluating the settings too early
jnoob22 has quit
Zeo has quit
snurfery joined the channel
there already exists two stages in django, pre and post evaluating the settings. Some modules will target the pre stage but there is no mechanism to avoid confusion. I guess django.setup could resolve this if it raises an exception if a setting is accessed before .setup is called
whitglint joined the channel
Gambit- joined the channel
SoftwareMaven has quit
dbieon12 joined the channel
dbieon12
hello how is everyone
furoido joined the channel
munichlinux has quit
munichlinux joined the channel
does anyone know a method to start a django project with an existing directory/files?
munichlinux has quit
scriptThis joined the channel
mattmcc
dbieon12: See the template argument
dbieon12
i copied my directory from an old machine onto a new one and just installed django
mattmcc
Oh, so you're not really starting a project.
Are you using virtualenv?
tightflks_ joined the channel
PantsOfChoco has quit
josephkokenge joined the channel
tightflks_ has quit
garrypolley joined the channel
ArcTanSusan has quit
Laybunz has quit
dray3 has quit
milky joined the channel
dray3 joined the channel
bradfordtoney has quit
garrypolley has quit
mstrcnvs has quit
k_sze[work] joined the channel
amyrlam has quit
bradfordtoney joined the channel
tightflks_ joined the channel
d3c0 joined the channel
ArcTanSusan joined the channel
emperorcezar joined the channel
tightflks_ has quit
chrisjones has quit
mstrcnvs joined the channel
yoyoohrho joined the channel
thepeculiarform has quit
knownasilya joined the channel
askvictor has quit
SoftwareMaven joined the channel
ArcTanSusan has quit
marcules has quit
munichlinux joined the channel
bradfordtoney has quit
kl4us has quit
rozwell has quit
bradfordtoney joined the channel
kl4us joined the channel
georgeirwin joined the channel
bradfordtoney has quit
caen23 has quit
crazydiamond joined the channel
Bryson_ has quit
tightflks_ joined the channel
ryanhiebert joined the channel
jnoob22 joined the channel
ryanhiebert
Will south fall back to Django 1.7 migrations if they aren't south migrations? I have multiple apps in a project, and I don't know if I'll be able to move them all to the new migrations at once.
georgeirwin has quit
FunkyBob
no, it won't
jnoob22
Is it possible to have one model write it's data to an relational db and another model write to something like mongodb?
FunkyBob
jnoob22: not yet...
jnoob22
darn :(
FunkyBob
what are you using mongo for?
ryanhiebert
blast. OK. thanks FunkyBob
jnoob22
to hold variable data from tests that don't fit neatly into a relational database and for speed for search/output since this is also going to fill up with many many rows of data.
tightflks_ has quit
FunkyBob
right... and we all know sql DBs cn't deal with millions of rows... oh wait...
jnoob22
maybe i can write something manually for it.
FunkyBob
can't just use a JSON field?
jnoob22
didn't know we had that ... <off to look up JSONField> ;)
FunkyBob
it's not part of django core
but there are a number of 3rd part apps to add one... several using the postgres native json field type
jnoob22
still i do wonder FunkyBob ... if db's can do that with speed why is a company say like Alfresco using Solr/Lucene for searches?