> Surprisingly there isn't any junction.exe in the utilities folder (and
> neither in other folders as well) in the instanddjango distribution. I
> thought I had a backdated installer and so I've just downloaded the
> package again a few while ago but still couldn't found that
> junction.exe in current package. Are you using any older version of
> instantdjango package which used to include the junction tool (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)
> provided by system internals, but removed that tool from recent
> package anyhow?

> But AFAIK, junction.exe can't help to resolve/understand/transform
> symlinks created in unix platform to windows equivalent which could
> solve this recent gdata symlink issue. I'm not sure how everything is
> being special in your environment, but I must congratulate for you to
> have a better luck than me.

> Anyway, I think this investigation for me to solve this gdata symlink
> issue was very useful and I learned quite a few things.

> Allan,

> Did you find any luck with your pinax installation issue in windows
> platform?

> I've created a patch for django-hotclub/apps/djangologging/
> management.py file so that django logging middleware don't intercept
> the exception responses generated by django which is djangologging's
> current behaviour and the cause for the misleading exception stack
> trace in the browser instead of showing the actual and very useful
> exception info generated by django for any exception. I know I need to
> place this patch in djangologging's site, but also sharing it here if
> anyone needs it while using pinax due to pinax's dependency on
> djangologging app. The block next to my signature is the patch code.

> Thanks & Regards,
> Shihan

> Index: middleware.py
> ===================================================================
> --- middleware.py       (revision 25)
> +++ middleware.py       (working copy)
> @@ -14,6 +14,7 @@
>  from django.shortcuts import render_to_response
>  from django.template import loader
>  from django.utils.cache import add_never_cache_headers
> +from django.http import
> Http404,HttpResponseBadRequest,HttpResponseForbidden,HttpResponseNotAllowed ,HttpResponseNotFound,
> HttpResponseServerError
>  try:
>      from django.utils.encoding import smart_str
>  except ImportError:
> @@ -140,6 +141,9 @@

>      def process_response(self, request, response):

> +        if isinstance(response,
> (Http404,HttpResponseBadRequest,HttpResponseForbidden,HttpResponseNotAllowe d,HttpResponseNotFound,
> HttpResponseServerError,)):
> +            return response
> +
>          if logging_output_enabled and \
>                  request.META.get('REMOTE_ADDR') in
> settings.INTERNAL_IPS and \
>                  not getattr(response, SUPPRESS_OUTPUT_ATTR, False):

> On Aug 20, 1:27 am, Robin <rober...@gmail.com> wrote:

> > Hello Shihan,

> > don't know exactly why you have problems with pinax and instantdjango
> > and I haven't. I didn't install anything special (gdata), and don't
> > make any special sym-link. I am using windows XP. And just grab a
> > fresh copy of pinax and everything works for me.

> > Related to the sym-link stuff, I was refering to 'junction' which is
> > bundled with instantdjango (instantdjango\Utilities\junction.exe) and
> > is suppose to do the same job as 'ln' on Unix, don't know if this is
> > usefull to you. Probably you can use this tool to create the proper
> > links related to gdata lib.

> > regards, r

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

> > > Hi Robin,

> > > I'm not sure how instantdjango helped to recover any sym-link related
> > > issues in windows platform. instantdjango is a nice package for
> > > newbies and I used to use instantdjango in my initial days with
> > > django. But when I learned the internals and felt comfortable to do
> > > the details by myself I switched to manual installation of django and
> > > django apps with standalone python-based installation to have greater
> > > flexibilities and controls.

> > > Basically what instantdjango does is just to provide all needed parts
> > > (along with some useful windows tools) along with a utility windows
> > > batch file to set all the necessary python path needed for django
> > > development. I go through and play with the batch file a lot but never
> > > saw anything related to handle sym-links (and its usual as sym-links
> > > are not supported in windows environment, so there should be no native
> > > way in windows batch to deal with unix sym-links).

> > > Anyway, which version of windows you are using with instant-django?

> > > Also are you using manual installation of gdata package using setup.py
> > > into your python_home/lib/site_packages/? Manual installation
> > > shouldn't have the sym-link issue but I liked to avoid it for any
> > > actively developed package checked out from svn repository to stay up-
> > > to-date with recent revisions and utilize the manual update of
> > > pythonpath environment variable. But if you are using the manual
> > > pyhtonpath update strategy like me can you please tell me the revision
> > > number of your gdata package (I think old revisions don't have this
> > > sym-link issue)?

> > > BTW, I'm also a newbie and don't think me otherwise. I am just a bit
> > > curious to know the actual fact that helped you to overcome the gdata
> > > package's sym-link issue in windows platform.

> > > Regards,
> > > Shihan

> > > On Aug 19, 2:51 am, Robin <rober...@gmail.com> wrote:

> > > > Hi !

> > > > as a possible solution for django in windows, I think also have some
> > > > solution for the sym-links, is the instant django:http://www.instantdjango.com/

> > > > And also helps a lot with the testing and development of django, and
> > > > also pinax. I have tried it and works fine with the latest version of
> > > > pinax and no problem found there.

> > > > r

> > > > On Aug 17, 4: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