Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-14 Thread Thomas Lockhart
On 9/14/12 10:07 AM, Bob Aalsma wrote: Well, I have tried your suggestion in all places I could think of and none of those helped: the createsuperuser kept returning the same error message. I posted this as a reply some 24 hours ago. Yes, with no details of what "all the places I could think

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-14 Thread Bob Aalsma
Well, I have tried your suggestion in all places I could think of and none of those helped: the createsuperuser kept returning the same error message. I posted this as a reply some 24 hours ago. Op donderdag 13 september 2012 16:58:11 UTC+2 schreef Bob Aalsma het volgende: > > I'm a newbie

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-14 Thread Thomas Lockhart
On 9/14/12 3:47 AM, Bob Aalsma wrote: SOLVED by Tom Evans: insert unset LC_CTYPE ; export LANG="nl_NL.UTF-8" into .bash_profile That is a solution, but depends on who is running and whether it is a login shell. I strongly recommend adding the lines I mentioned earlier to the top of your

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-14 Thread Tom Evans
On Fri, Sep 14, 2012 at 10:26 AM, Bob Aalsma wrote: > macpro1:~ bobaalsma$ locale > LANG= > LC_COLLATE="C" > LC_CTYPE="UTF-8" > LC_MESSAGES="C" > LC_MONETARY="C" > LC_NUMERIC="C" > LC_TIME="C" > LC_ALL= > macpro1:~ bobaalsma$ python -c 'import locale; print >

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-14 Thread Bob Aalsma
SOLVED by Tom Evans: insert unset LC_CTYPE ; export LANG="nl_NL.UTF-8" into .bash_profile Op donderdag 13 september 2012 16:58:11 UTC+2 schreef Bob Aalsma het volgende: > > I'm a newbie following the tutorial. In this, creating a superuser is > described, using > > manage.py createsuperuser

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-14 Thread Bob Aalsma
macpro1:~ bobaalsma$ locale LANG= LC_COLLATE="C" LC_CTYPE="UTF-8" LC_MESSAGES="C" LC_MONETARY="C" LC_NUMERIC="C" LC_TIME="C" LC_ALL= macpro1:~ bobaalsma$ python -c 'import locale; print locale.getdefaultlocale()' Traceback (most recent call last): File "", line 1, in File

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-14 Thread Tom Evans
On Fri, Sep 14, 2012 at 8:52 AM, Bob Aalsma wrote: > The command & error from createsuperuser: > macpro1:dripFeedSite bobaalsma$ python manage.py createsuperuser > … Can I ask you to try some things, just to see how your environment is setup. All of these commands

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-14 Thread Bob Aalsma
The command & error from createsuperuser: macpro1:dripFeedSite bobaalsma$ python manage.py createsuperuser Traceback (most recent call last): File "manage.py", line 19, in execute_from_command_line(sys.argv) File "/Library/Python/2.7/site-packages/django/core/management/__init__.py",

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-13 Thread Thomas Lockhart
On 9/13/12 10:37 AM, Bob Aalsma wrote: Hmm, I'd seen this solution in http://keeyai.com/2012/02/17/django-deployment-create-superuser-fails-with-locale-error/ but was reluctant to use this as " I have no idea if this causes any negative side effects." A running system is not usually

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-13 Thread Kurtis Mullins
Try installing python using "brew" or another packaging utility On Thu, Sep 13, 2012 at 1:54 PM, Bob Aalsma wrote: > Umm, could you be more specific about how/where to put this? > All the combinations and location I could think of will all still give the > same

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-13 Thread Bob Aalsma
Umm, could you be more specific about how/where to put this? All the combinations and location I could think of will all still give the same error... Op donderdag 13 september 2012 16:58:11 UTC+2 schreef Bob Aalsma het volgende: > > I'm a newbie following the tutorial. In this, creating a

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-13 Thread Bob Aalsma
Hmm, I'd seen this solution in http://keeyai.com/2012/02/17/django-deployment-create-superuser-fails-with-locale-error/ but was reluctant to use this as " I have no idea if this causes any negative side effects." So that is the official repair? OK. Thanks! Op donderdag 13 september 2012

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-13 Thread Tom Lockhart
On 2012-09-13, at 10:17 AM, Bob Aalsma wrote: > Django 1.4.1 > Python 2.7.3 > OS X 10.7.4 Ah, OS X… You need to (slightly) modify your manage.py file to add this near the top: import os os.environ.setdefault('LANG','en_CA') substituting your favorite language setting of course. hth

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-13 Thread Bob Aalsma
Django 1.4.1 Python 2.7.3 OS X 10.7.4 Op donderdag 13 september 2012 19:12:30 UTC+2 schreef creecode het volgende: > > Which version of django are you using? > > On Thursday, September 13, 2012 7:58:11 AM UTC-7, Bob Aalsma wrote: > > I'm a newbie following the tutorial. In this, creating a

Re: newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-13 Thread creecode
Which version of django are you using? On Thursday, September 13, 2012 7:58:11 AM UTC-7, Bob Aalsma wrote: I'm a newbie following the tutorial. In this, creating a superuser is > described, using > > manage.py createsuperuser --username=joe --email=j...@example.com > > > > Using this leads

newbie: patch required? procedure? [closed ticket 16017 / createsuperuser]

2012-09-13 Thread Bob Aalsma
I'm a newbie following the tutorial. In this, creating a superuser is described, using manage.py createsuperuser --username=joe --email=j...@example.com Using this leads to an error, which I could match to the closed ticket #16017. But I couldn't find how to proceed from there. It seems