Buildout and django-registration from repository for Django 1.5 -


i'd use buildout django-registration django 1.5, , have custom user using myuser(abstractuser). used recipe v0.8 , great. since, switched 1.5, remove userprofile , use custom myuser.

django-registration no longer work. i've been told should repository, , that's i'm trying do. i've in past used mr.developer newer version of django-tastypie, , tried reproduce same django-registration. have error while calling bin/buildout tho. let's first check buildout config:

[buildout] extensions = mr.developer parts = myquivers eggs =     django-registration include-site-packages = false versions = versions sources = sources auto-checkout =     django-registration  [sources] django-registration = hg https://bitbucket.org/ubernostrum/django-registration  [versions] django = 1.5  [myquivers] recipe = djangorecipe settings = development eggs = ${buildout:eggs} project = myquivers

pretty simple config. used work tastypie said, , i'm trying same steps: - python2.7 bootstrap.py - bin/buildout - bin/develop activate django-registration - bin/develop checkout django-registration - bin/myquivers syncdb - bin/myquivers runservser

but fails @ bin/buildout steps:

$ bin/buildout  getting distribution 'mr.developer'. got mr.developer 1.25. mr.developer: creating missing sources dir /home/damien/documents/projects/myquivers/src. mr.developer: queued 'django-registration' checkout. mr.developer: cloned 'django-registration' mercurial. develop: '/home/damien/documents/projects/myquivers/src/django-registration' traceback (most recent call last):   file "/tmp/tmpzldggg", line 13, in <module>     exec(compile(open('/home/damien/documents/projects/myquivers/src/django-registration/setup.py').read(), '/home/damien/documents/projects/myquivers/src/django-registration/setup.py', 'exec'))   file "/home/damien/documents/projects/myquivers/src/django-registration/setup.py", line 30, in <module>     version=get_version().replace(' ', '-'),   file "/home/damien/documents/projects/myquivers/src/django-registration/registration/__init__.py", line 5, in get_version     django.utils.version import get_version django_get_version importerror: no module named django.utils.version while:   installing.   processing develop directory '/home/damien/documents/projects/myquivers/src/django-registration'.  internal error occured due bug in either zc.buildout or in recipe being used: traceback (most recent call last):   file "/home/damien/documents/projects/myquivers/eggs/zc.buildout-2.1.0-py2.7.egg/zc/buildout/buildout.py", line 1923, in main     getattr(buildout, command)(args)   file "/home/damien/documents/projects/myquivers/eggs/zc.buildout-2.1.0-py2.7.egg/zc/buildout/buildout.py", line 466, in install     installed_develop_eggs = self._develop()   file "/home/damien/documents/projects/myquivers/eggs/zc.buildout-2.1.0-py2.7.egg/zc/buildout/buildout.py", line 707, in _develop     zc.buildout.easy_install.develop(setup, dest)   file "/home/damien/documents/projects/myquivers/eggs/zc.buildout-2.1.0-py2.7.egg/zc/buildout/easy_install.py", line 871, in develop     call_subprocess(args)   file "/home/damien/documents/projects/myquivers/eggs/zc.buildout-2.1.0-py2.7.egg/zc/buildout/easy_install.py", line 129, in call_subprocess     % repr(args)[1:-1]) exception: failed run command: '/usr/bin/python2.7', '/tmp/tmpzldggg', '-q', 'develop', '-mxn', '-d', '/home/damien/documents/projects/myquivers/develop-eggs/tmpym_dr9build'

checking @ error, first django seems not in system, , that's right, when entering python2.7 , try >>> import django, fails. that's normal , that's why i'm using buildout, not install system-wide django, locally project.

any idea how fix this? there better alternative taking repo version? please let me know, again, custom user/django 1.5/django-registration.

thanks!


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more