pinax is broken with current django trunk - django-hotclub

Message from discussion pinax is broken with current django trunk

M. N. Islam Shihan

More options Aug 16 2008, 11:10 am

From: "M. N. Islam Shihan" <mnis4...@gmail.com>

Date: Sat, 16 Aug 2008 08:10:30 -0700 (PDT)

Local: Sat, Aug 16 2008 11:10 am

Subject: Re: pinax is broken with current django trunk

  Reply to author
  |
  Forward
  | Print
  | View thread
  | Show original
  | Report this message
  | Find messages by this author
  

Hi,

At last I've fixed the issue with running pinax in windows. I'm
mentioning this as in my understanding any windows user will encounter
the same issue while running pinax and now I am thinking I was the
first pinax user in windows.

The issue was not with pinax instead with a third party library named
gdata on which pinax is dependednt. The gdata package is currently
shipped with two sym-links to the src/gdata and src/atom folders
within the actual site-packages/gdata.py-1.0.13 folder and as windows
does not support sym-linking to other folder as the unix genre OSs,
Pyhton was failing to locate this package. As a resolution I've copied
both the gdata and atom folders from site-packages/gdata.py-1.0.13/src
folder to site-packages/gdata.py-1.0.13 after removing the sym-links
to those folder. I believe somewhere in the pinax document (may be the
README file) this issue should be mentioned so that other windows
users like me won't have this issue.

Also another thing I must note this gdata issue could be fixed with
minimum investigation but it became worst and misleading due to an
issue with django-logging app which failed generically with all
exception pages generated by django. I am thinking to post a ticket
(or may be a patch) on django-logging site so that they update the
middleware code not to intercept the exception pages (as exception
pages have enough info than the logging middleware).

Thanks for your help.
Regards,
Shihan

On Aug 15, 10:16 pm, "M N Islam Shihan" <mnis4...@gmail.com> wrote:

> Hi Ariel,

> Thanks for your reply. I'm really ashamed to call pinax as pinux all the times. This really a silly mistake and I promise it won't be repeated again.

> I've tried all 2,3,4 solution strategies successively as you mentioned, but no luck.

> I'm really now feeling frustrating and as the errors are same I'm not replicating again.

> PS: Now I'm thinking the issue might be with the Python installation, I'm using Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) and am planning to use other versions as well.

> Thanks for your help.

> Regards,
> Shihan

> ----- Original Message -----
> From: Ariel Mauricio Nunez Gomez
> To: django-hotclub@googlegroups.com
> Sent: Friday, August 15, 2008 8:27 PM
> Subject: Re: Pinux is broken with current django trunk

> Sinhan,

> 1. Please, please stop refering to Pinax as Pinux.
> 2. Please delete all your browsers history and start from fresh database (drop your pg database or erase your dev.db)
> 3. Delete your pinax checkout and check it out again. (optional) (with svn, not hg or git)
> 4. Delete your django checkout and check it out again. (optional)

> Why am I suggesting all this? Well, in part because the session bug was a really nasty one and it was about sessions in your browser not found on the db. Please clean all your sessions, in browser and db and try again. Steps 3 and 4 are not required (in fact using pinax via svn is) there are a couple of problems with svn:externals linking to branches of some of the apps.

> Let me know how it goes. It is a shame you are having so much trouble, but remember: Calm after the storm.

> Best,
> Ariel

Reply to author Forward