> You can try the followings:

> 1. You can run the "setup.py build" and "setup.py install" commands
> from a shell prompt in your django-hotclub/site-packages/
> gdata.py-1.0.13 folder or manually update your pythonpath environment
> variable to have the full path of the django-hotclub/site-packages/
> gdata.py-1.0.13/src folder. Depending on your windows version setting
> this variable might vary : but the usual steps to get the environment
> variable section is "Control Panel->System->Advanced->Environment
> variables"

> 2. As manage.py in "django-hotclub/pinax" folder set the necessary
> python paths, you can try removing anything named "gdata" and "atom"
> found in "django-hotclub/site-packages/gdata.py-1.0.13" folder, copy
> the contents of "django-hotclub/site-packages/gdata.py-1.0.13/src"
> into "django-hotclub/site-packages/gdata.py-1.0.13" folder. If this
> doesn't work, open the "packages.pth" file found in "django-hotclub/
> trunk/site-packages" using any text editor like notepad++ or editplus
> (you shouldn't use notepad as it can't understand unix newline chars)
> add any text to that file, save it, remove the added text and save it
> again. What you'll do with this can be done very easily in an unix box
> using touch command but in windows platform there isn't any native
> equivalent.

> 3. Make sure you ran "manage.py syncdb" command at least once from the
> "django-hotclub/pinax" folder.

> If the above steps doesn't work for you anyhow, open the settings.py
> file "django-hotclub/pinax" folder and comment out the line

> 'djangologging.middleware.LoggingMiddleware',

> in "MIDDLEWARE_CLASSES" configuration by appending a # before that
> line to view the actual error that is happening in your browser. You
> can also post that response so that we can help you to find out and
> resolve the actual issue.

> Regards,
> Shihan

> On Aug 17, 8:50 pm, Allan <amet...@mindspring.com> wrote:

> > I seem to be having the same issue (Windows, django-1.0-beta-1, pinax
> > Rev: 769).  Unfortunately for me, replacing the symlinks in gdata
> > didn't seem to resolve the issue.

> > I only have about 45 minutes of experience with pinax thus far, so my
> > problem could definitely be a newbie issue.  Any suggestions on how I
> > can debug this?  My stack trace appears below.

> > Traceback (most recent call last):

> >   File "c:\python25\Lib\site-packages\django\core\servers
> > \basehttp.py", line 277, in run
> >     self.result = application(self.environ, self.start_response)

> >   File "c:\python25\Lib\site-packages\django\core\servers
> > \basehttp.py", line 634, in __call__
> >     return self.application(environ, start_response)

> >   File "c:\python25\Lib\site-packages\django\core\handlers\wsgi.py",
> > line 220, in __call__
> >     response = middleware_method(request, response)

> >   File "C:\Users\allan\src\django\app\pinax\apps\djangologging
> > \middleware.py", line 153, in process_response
> >     self._rewrite_html(request, response)

> >   File "C:\Users\allan\src\django\app\pinax\apps\djangologging
> > \middleware.py", line 187, in _rewrite_html
> >     response.content = close_body_re.sub(r'%s\1' % footer,
> > response.content)

> >   File "c:\python25\lib\re.py", line 261, in _subx
> >     template = _compile_repl(template, pattern)

> >   File "c:\python25\lib\re.py", line 248, in _compile_repl
> >     raise error, v # invalid expression

> > error: bad group name