Closed GoogleCodeExporter closed 9 years ago
Our web expert is off-site now, but maybe he ca have a look.
Mariano, do you have an idea what's going on?
Original comment by andre.knoerig@gmail.com
on 12 Mar 2010 at 9:21
This might possibly be due to Pinax requiring a particular version of Django--I
think
it might be 1.0.4?
Original comment by irasc...@gmail.com
on 12 Mar 2010 at 12:05
Ok, I downgraded to django 1.0.4 it fixed the NullBoolean stuff when running
syncdb,
but I'm still getting the import error with the stack trace I pasted.
Original comment by osborn.s...@gmail.com
on 12 Mar 2010 at 9:38
I did some version wrangling. Had to get an older version of
django-filebrowse, and
pull django-pages from git because the release version seems to be missing
widgets.py
Still fighting random errors. Is there no better way to get this running?
Original comment by osborn.s...@gmail.com
on 13 Mar 2010 at 12:01
In the documentation at ixds private wiki, there's a little explanation about
the
main problems that i got setting up the djnago-pinax environment.
The main problem is that the updating process it's kind heavy, i think mostly
because
many of the django apps that pinax uses, are development versions... you cannot
actually rely on them, yet
I tried the update process some time ago, and I gave up and sticked to the
original
environment: pinax 0.7.3 and django 1.0.2
With Jonathan we tried to set a django development environment in a windows
machine,
but we couldn't find the 0.7.3 version of pinax. I guess it can be dragged from
linux
machine at ixds (the process is lighlty described also in the ixds wiki).
Original comment by meru...@gmail.com
on 13 Mar 2010 at 12:25
I think I finally have everything working (or at least mostly working) and feel
some
affirmation for choosing to go with a less feature rich, but workable stack in
the
past - Pinax is a mess.
Original comment by osborn.s...@gmail.com
on 14 Mar 2010 at 10:40
We completely agree.
Original comment by irasc...@gmail.com
on 14 Mar 2010 at 11:40
Original comment by irasc...@gmail.com
on 17 Mar 2013 at 6:42
Issue has moved to new issue tracker at github. Please continue the discussion
at https://github.com/fritzing/fritzing-app/issues
Original comment by andre.knoerig@gmail.com
on 23 Sep 2014 at 3:37
Original issue reported on code.google.com by
osborn.s...@gmail.com
on 11 Mar 2010 at 6:32