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

Update Django version #26

Open
odyssey4me opened this issue Jul 12, 2013 · 2 comments
Open

Update Django version #26

odyssey4me opened this issue Jul 12, 2013 · 2 comments

Comments

@odyssey4me
Copy link
Contributor

It'd be ideal to be able to make use of the more recent versions of DJango. I don't know how easy it will be to merge the updates in?

@willkelly
Copy link
Contributor

I made a new branch (django1.5) with an updated django. Everything appears to be working, but if you could check it out and make sure it meets your needs, I would appreciate it. I'll merge when I hear back, assuming all is well.

https://github.com/rcbops/djeep/tree/django1.5

@odyssey4me
Copy link
Contributor Author

When trying to use curl to change the 'local boot' checkbox, the following error occurrs:

Piston/0.2.3rc1 (Django 1.5.5) crash report:

Traceback (most recent call last):

  File "/opt/djeep/.kick-venv/src/django-piston/piston/handler.py", line 134, in update
    return rc.ALL_OK

  File "/opt/djeep/.kick-venv/src/django-piston/piston/utils.py", line 55, in __getattr__
    class HttpResponseWrapper(HttpResponse):

  File "/opt/djeep/.kick-venv/src/django-piston/piston/utils.py", line 82, in HttpResponseWrapper
    content = property(HttpResponse._get_content, _set_content)

AttributeError: type object 'HttpResponse' has no attribute '_get_content'

This appears to be a well known issue: http://stackoverflow.com/questions/16294518/httpresponse-has-no-attribute-get-content

And there are some forks to deal with it, for example: https://bitbucket.org/spookylukey/django-piston

After trying one or two django-piston forks, I've verified that the above-mentioned fork works.

I've included the fix in #34

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

2 participants