andreirk / django-hotclub

Automatically exported from code.google.com/p/django-hotclub
0 stars 0 forks source link

Installation using buidout is broken #195

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Following the installation instructions at 
http://pinaxproject.com/docs/trunk/install.html (using 
buildout), severall apps are not installed correctly. When running ./manage.py 
syncdb in the basic 
project, an error appears that the django_openid module cannot be found. 
Subsequent runs of 
buildout alternate between the missing django_openid module and (in the second 
case) the missing 
emailnotifications, mailer and uni_forms modules. Possibly more modules are 
affected, I did not try 
with the complete project.

I tested this behaviour under Mac OS 10.5.6 as well as Ubuntu Linux 8.04. 
Installing using just pip 
works fine.

Original issue reported on code.google.com by sjaensch on 6 Mar 2009 at 3:40

GoogleCodeExporter commented 9 years ago
For the record, we talked on IRC about that prior the ticket.

Original comment by leidel on 6 Mar 2009 at 3:52

GoogleCodeExporter commented 9 years ago
If it means anything, our group has moved away from buildout.

Original comment by pyDanny on 13 Mar 2009 at 4:42

GoogleCodeExporter commented 9 years ago

Original comment by jtau...@gmail.com on 16 Mar 2009 at 3:11

GoogleCodeExporter commented 9 years ago
Just ran the buildout install and I'm getting error messages seemingly around
python-openid. I tried doing a pip-based install followed by doing buildout (in 
the
same virtualenv) and I tried just going straight to buildout and the error 
appears to
be the same. I've attached my eggs-log.txt file from the straight buildout 
install. 

Original comment by winhamwr on 26 Mar 2009 at 12:37

Attachments:

GoogleCodeExporter commented 9 years ago
I've had this same issue today. Without knowing buildout myself, there appears 
to be
an issue with the syntax of the line

indexes http://pypi.pinaxproject.com/

Commenting it out works around the problem, although it's not the last problem 
you
will encounter if you follow the installation instructions :)

I'm using OS X 10.5.6 and Python 2.5.1

Original comment by atkins...@gmail.com on 26 Mar 2009 at 5:06

GoogleCodeExporter commented 9 years ago
All working now for me.

All subsequent problems I encountered were because of pre-existing PYTHONPATH 
and
DJANGO_SETTINGS_MODULE environment variables.

I commented these out of my ~/.profile and then deleted the whole pinax-env/ 
tree and
started again. I just used pip and not buildout and everything seems to be 
working well.

Original comment by atkins...@gmail.com on 26 Mar 2009 at 5:51

GoogleCodeExporter commented 9 years ago
atkinsonr: That is not the scope of the bug. Using pip instead of buildout 
works, as the last sentence of the 
report states. Buildout is broken. Commenting out the indexes line fixes the 
build process, but you are left with 
a broken system. Several apps cannot be imported, the sample projects won't 
work.

Original comment by sjaensch on 26 Mar 2009 at 1:50

GoogleCodeExporter commented 9 years ago
sjaensch: for me it doesn't look working with pip either. See 
http://code.google.com/p/django-hotclub/issues/detail?id=211

Original comment by khame...@gmail.com on 28 Mar 2009 at 10:12

GoogleCodeExporter commented 9 years ago
Moved to cpc

Original comment by pyDanny on 31 Mar 2009 at 2:29

GoogleCodeExporter commented 9 years ago

Original comment by pyDanny on 31 Mar 2009 at 2:41