Error: <django.utils.functional.__proxy__ object trying to install pinax

[Daniel Remeseiro]

Hi, this is my first try with Pinax, i am really excited to test
it.... but...

I am trying to install Pinax following the instructions at
http://pinaxproject.com/docs/trunk/install.html : doing svn checkout
and running the ./manage.py syncdb script
on the complete_project folder, but when i run this script all i get
is this error:

./manage.py syncdb

Error: <django.utils.functional.__proxy__ object at 0x1b2af10>

(the number could be not the same)


I am on Mac os X Leopard, but i have tried on Ubuntu with same
results.

What i am doing wrong?

(i am pretty sure i have Django installed)

[greg newman]

What release of Django are you running and what version of Python?

greg newman
http://20seven.org

[Daniel Remeseiro]

daniel$ python -V
Python 2.5.2


and Django 1.0

On 25 oct, 18:41, greg newman <g...@20seven.org> wrote:
> What release of Django are you running and what version of Python?
>

> greg newmanhttp://20seven.org

[greg newman]

Is there more to the error or just what you posted

greg newman
http://20seven.org

[Daniel Remeseiro]

no more output.... the scripts ends and thats all...

Error: <django.utils.functional.__proxy__ object at 0x1b2af10>

(showing in color red)

On 25 oct, 18:52, greg newman <g...@20seven.org> wrote:
> Is there more to the error or just what you posted
>

[greg newman]

I can't reproduce. I wonder if you're using Django trunk and this is
a new issue.

greg newman
http://20seven.org

[Daniel Remeseiro]

there was some old django instalation garbagge on my site-packages
folder: a 0.96 django egg-info file
once deleted i am able to setup the basic_project ( everything ok,
the server runs ok ...)

But when i try with the complete_project once again the same error:

Error: <django.utils.functional.__proxy__ object at 0x1ada850>

I have tried to delete again Django (clenaning all files)& pinax
completely 3 times with the same behaviour....



PD:Could be the google app engine instalation ? i see some kind of
references to Django into it...

[greg newman]

Google app engine will have no affect on your pinax install.
Do you have all the libs installed that come with Pinax?

greg newman
http://20seven.org

[Mutaz]

Hi

I'm getting the same message when trying to syncdb Pinax
complete_projects. <django.utils.functional.__proxy__ object at
0x13bb2d0>


I have:
Pinax trunk
Django 1.0
Python 2.5.2

And Mac 10.5.5

What should I do to have it running?

Thanks

On Oct 26, 2:31 am, greg newman <g...@20seven.org> wrote:
> Google app engine will have no affect on your pinax install.
> Do you have all the libs installed that come with Pinax?
>

> greg newmanhttp://20seven.org

[mrowe]

Just to add a data point, I'm getting the same thing:

pinax/projects/complete_project $ ./manage.py syncdb
Error: <django.utils.functional.__proxy__ object at 0x13fb970>

I'm running OS X 10.5.5, Python 2.5.1, django trunk and pinax trunk
(both updated an hour or two ago).

If I get a chance I will try with django 1.0 tomorrow.

[greg newman]

Are you running pinax-0.5.0rc2? It's been reported in the irc channel
that this release fixes this error.

greg newman
http://20seven.org

[Mautaz Alkasem]

I got rid of this error!
I did nothing but installed PIL and then ran sysdb and everything went fine.
Though the error message "django.utils.functional.__proxy__ object at> 0x13bb2d0"  has nothing to do with PIL installation, but it has been fixed!!
Just make sure that PIL is installed correctly and support/have access to the required imaging packages.

Hope that helps.

[greg newman]

Thanks for chiming in Mautaz!

greg newman

http://20seven.org

[Mutaz Qasem]

didn't get you! do you mean I interrupted you?

[greg newman]

No, meaning you've confirmed you've rectified your error. :)

greg newman

http://20seven.org

[Mutaz Qasem]

Thank you too greg :)

[mrowe]

Hmm, installing PIL worked for me too. Thanks Mautaz!

On Oct 27, 11:20 pm, "Mautaz Alkasem" <muta...@gmail.com> wrote:
> I got rid of this error!
> I did nothing but installed PIL and then ran sysdb and everything went fine.
> Though the error message "django.utils.functional.__proxy__ object at>
> 0x13bb2d0"  has nothing to do with PIL installation, but it has been fixed!!
> Just make sure that PIL is installed correctly and support/have access to
> the required imaging packages.
>
> Hope that helps.
>

[James Tauber]

The root cause of this error is that photologue is trying to use
ugettext_lazy when throwing an exception that PIL is missing.

The obvious fix is to make sure PIL isn't missing, but photologue
should be changed. Using ugettext_lazy won't work on an exception
message that bubbles to the top because once it gets to the top, you
aren't in normal program flow so you can't assume stuff is there.

Immediate localization probably isn't a good idea either. My suggested
fix to photologue is to not use i18n/l10n at all on exception messages.

James

[Mutaz Qasem]

Most welcome :)

[Justin]

I'm the author of Photologue. Greg notified me of this problem this
morning so I thought I'd give those affected an update. None of the
other exceptions in Photologue are run through the translation
machinery and ugettext_lazy will do that when inserted into a
bytestring. This was an oversight and is fixed in Photologue r354. I
don't get a lot of users trying to install Photologue alone without
PIL so I appreciate you bringing this to my attention. Please feel
free to use the issue tracker on the Photologue project site for any
problems you come across specific to the library.

http://code.google.com/p/django-photologue/issues/list

- Justin

On Oct 28, 6:11 am, "Mutaz Qasem" <muta...@gmail.com> wrote:
> Most welcome :)
>