search

estebistec / django-twitter-bootstrap

This package provides a Django app whose static folder contains the sources of Twitter Bootstrap, nothing more and nothing less.
MIT License
64 stars 22 forks source link

python setup.py install vs. pip install #20

Closed pquentin closed 9 years ago

pquentin commented 9 years ago

Running python setup.py install only produces one file in the virtualenv: lib/python3.4/site-packages/django_twitter_bootstrap-3.2.0_1-py3.4.egg.

However, running, pip install django-twitter-bootstrap produces django_twitter_bootstrap-3.2.0_1-py3.4.egg-info (so, +info) and lib/python3.4/site-packages/twitter_bootstrap. What's the difference? How can I properly install django-twitter-bootstrap with a local git clone?

Thank you.

pquentin commented 9 years ago

I needed to git clone --recursive, sorry for the noise.

pquentin commented 9 years ago

However, I don't know how to get twitter_bootstrap installed in site-packages. python setup.py install doesn't seem to do it.

estebistec commented 9 years ago

@pquentin Sorry for not noticing this (yikes, this must've gotten buried in a mark-as-read with a lot of other noise).

So, while this method of installation from source doesn't leave the folder behind, the .egg is pretty much a zip of the package, on the path and it should be importable (though, the static files may not be found this way).

However, why install this way as opposed to a typical pip install (where you get pretty much everything you need).

Now, if you're dev'ing on this package, then I would suggest a dev-install of the package. So instead of python setup.py install, do pip install -e ..

Tell me if I'm missing something else though.

estebistec commented 9 years ago

Also, given how long I missed this issue, perhaps I should relinquish primary maintenance of this package :/

Are you still using it much?

pquentin commented 9 years ago

Yeah, I was trying to fix an issue, and at the time I used python setup.py install. I now usually do python setup.py develop - thanks for mentioning dev-install and pip install -e!

No worries at all for the delay, it wasn't a blocking issue, and I used django-twitter-bootstrap for some time without issues. I did stop using django-twitter-bootstrap and I'm now including bootstrap as a git submodule - this has its own issues; I still don't know what's the best way to work with bootstrap for a project that is supposed to continue to evolve year after year.

Thank you for thinking about me!