Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

collectstatic breaks if django_dajax installed as a zipped egg #53

Open
ngkabra opened this issue Jan 31, 2013 · 8 comments
Open

collectstatic breaks if django_dajax installed as a zipped egg #53

ngkabra opened this issue Jan 31, 2013 · 8 comments

Comments

@ngkabra
Copy link

ngkabra commented Jan 31, 2013

In my setup, I found that if django_dajax was installed as a zipped egg (e.g. easy_install -z django_dajax), then collectstatic failed to find dajax/jquery.dajax.core.js and other dajax static files. The problem went away when I forced easy_install to do an unzipped install (easy_install -Z django_dajax).

I have not really determined whether this is a problem with DajaxiceFinder, or Django staticfiles in general, or whether it was with django-pipeline (which I am also using) - so I cannot give a suggested fix for sure.

However, putting up the issue here, along with the suggested workaround (easy_install -Z) for the benefit of anyone else who runs into this problem.

@ghost
Copy link

ghost commented Jan 31, 2013

I don't use django-pipeline, but I have installed django_dajax via PIP with no problem.

@ngkabra
Copy link
Author

ngkabra commented Feb 1, 2013

Like I said this is only a problem when it gets installed as a zipped up egg.

When installing with easy_install, whether it will get installed as a zipped up egg, or an unzipped directory depends upon the site wide configuration settings. So it will not affect everyone.

But, for example, on webfaction (which is one of the popular python hosting providers), it gets installed by default as a zipped up egg and runs into this problem. Over the weekend I will try to investigate some more and find out what is the exact cause of the problem.

@ghost
Copy link

ghost commented Feb 1, 2013

Ok.
I recommend you Heroku, where you can install the packages via pip.

@ngkabra
Copy link
Author

ngkabra commented Feb 2, 2013

That's not the point. The point is that dajax should work cleanly irrespectively of which platform/package installer the users are using.

@ghost
Copy link

ghost commented Feb 2, 2013

Yes, you are right.
I have recommended you other service for help you. Because I have thought that it was urgent for you fix that.

@dekoza
Copy link

dekoza commented Jun 5, 2014

I can confirm this issue with other packages zipped as eggs in Django 1.6.5. Looks like an issue with Django itself.

@luckydonald
Copy link

It is somehow filed as issue in django: https://code.djangoproject.com/ticket/22774

@luckydonald
Copy link

http://stackoverflow.com/a/29124937/3423324 brings a solution:

setup.py

setup(
    ...
    zip_safe = False,
)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants