RE: Re: [viewvc-users] About python crypt module introduced in standalone.py in viewvc-1.1.7
LiuYan 刘研 <[email protected]>
| Newsgroups | gmane.comp.version-control.cvs.viewcvs.user |
|---|---|
| Message-ID | <1856458640.6838.1289928149326.JavaMail.httpd__33044.7415392429$1289928160$gmane$org@localhost> |
> On 11/16/2010 10:41 AM, C. Michael Pilato wrote: > > On 11/16/2010 12:10 AM, LiuYan 刘研 wrote: > >> I notice python crypt module was introduced in standalone.py in > >> viewvc-1.1.7 because I got an 'no module named crypt' when running > >> 'python.exe standalone.py'. > >> > >> After gooooooogled for a long time, I got the cause: python crypt module > >> is only for linux/unix system, not for windows system. so standalone.py > >> will not run on windows system. > >> > >> Will the crypt module dependency be kept in future versions? > >> > >> btw: someone suggest to use Python in Cygwin, it sounds should be a > >> solution, but I don't know if there's a chance to cause another issue... > > > > Eek. My fault, completely. I'll fix this in the next release. Until then, > > you should be able to comment out the 'import crypt' line from standalone.py: > > > > #import crypt > > > > I've tracked this bug and fix in issue #471[1]. If you'd rather not > hand-tweak your ViewVC code, you might consider grabbing the nightly > build[2] tomorrow to use on your servers. So far, that build differs from > 1.1.7 only by these two fixes: > > * fix slowness triggered by allow_compress=1 configuration (issue #467) > * fix standalone.py Windows regression (issue #471) > > Sorry for breaking ViewVC on Windows. > > -- C-Mike > > [1] http://viewvc.tigris.org/issues/show_bug.cgi?id=471 > [2] http://viewvc.org/nightly/ > > -- > C. Michael Pilato <cmpilato at collab dot net> > CollabNet <> www.collab.net <> Distributed Development On Demand Thank you Michael! I'll try nightly build tomorrow! ------------------------------------------------------ http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2682253 To unsubscribe from this discussion, e-mail: [[email protected]].