Web dependency version issues

[davidperrenoud]

From osborn.s...@gmail.com on March 11, 2010 01:32:40

I'm trying to get the web code working and running into some issues with dependencies.

My steps for bootstraping are:

1. virtualenv .
2. . bin/activate
3. pip install -r requirements.txt
4. ./manage.py syncdb

Which results in Error: One or more models did not validate: forum.thread: "sticky": BooleanFields do not accept null values. Use a NullBooleanField instead. forum.thread: "closed": BooleanFields do not accept null values. Use a NullBooleanField instead.

But if I hack the fields to be NullBooleanField and run the code I get the following stack trace.

1. ./manage.py runserver

Traceback: File "/Library/Python/2.6/site-packages/Django-1.1.1-py2.6.egg/django/core/handlers/base.py" in get_response

1. request.path_info) File "/Library/Python/2.6/site-packages/Django-1.1.1-py2.6.egg/django/core/urlresolvers.py" in resolve
2. for pattern in self.url_patterns: File "/Library/Python/2.6/site-packages/Django-1.1.1-py2.6.egg/django/core/urlresolvers.py" in _get_url_patterns
3. patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module) File "/Library/Python/2.6/site-packages/Django-1.1.1-py2.6.egg/django/core/urlresolvers.py" in _get_urlconf_module
4. self._urlconf_module = import_module(self.urlconf_name) File "/Library/Python/2.6/site-packages/Django-1.1.1-py2.6.egg/django/utils/importlib.py" in import_module
5. import(name) File "/Users/steven/Projects/electronics/fritzing-read-only/web/fritzing/../fritzing/urls.py" in
6. admin.autodiscover() File "/Library/Python/2.6/site-packages/Django-1.1.1-py2.6.egg/django/contrib/admin/init.py" in autodiscover
7. import_module("%s.admin" % app) File "/Library/Python/2.6/site-packages/Django-1.1.1-py2.6.egg/django/utils/importlib.py" in import_module
8. import(name) File "/Users/steven/Projects/electronics/fritzing-read-only/web/fritzing/../fritzing/apps/projects/admin.py" in
9. from pages.admin.widgets import markItUpMarkdown

Exception Type: ImportError at / Exception Value: No module named widgets

Original issue: http://code.google.com/p/fritzing/issues/detail?id=1021

[davidperrenoud]

From andre.knoerig@gmail.com on March 12, 2010 01:21:50

Our web expert is off-site now, but maybe he ca have a look.

Mariano, do you have an idea what's going on?

Owner: merunga
Labels: -Type-Defect Type-Other Component-Web

[davidperrenoud]

From irasc...@gmail.com on March 12, 2010 04:05:37

This might possibly be due to Pinax requiring a particular version of Django--I think it might be 1.0.4?

[davidperrenoud]

From osborn.s...@gmail.com on March 12, 2010 13:38:07

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.

[davidperrenoud]

From osborn.s...@gmail.com on March 12, 2010 16:01:05

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?

[davidperrenoud]

From meru...@gmail.com on March 12, 2010 16:25:08

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).

[davidperrenoud]

From osborn.s...@gmail.com on March 14, 2010 15:40:20

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.

[davidperrenoud]

From irasc...@gmail.com on March 14, 2010 16:40:18

We completely agree.

[davidperrenoud]

From irasc...@gmail.com on March 16, 2013 23:42:13

Owner: danielcl...@gmail.com