Roundup Tracker - Issues

Message4979

Author rouilj
Recipients matt109, rouilj
Date 2013-12-27.17:53:21
Message-id <20131227175320.38211BF2@vm72.cs.umb.edu>
In-reply-to Your message of "Fri, 27 Dec 2013 17:35:59 GMT." <1388165759.72.0.941138301996.issue2550827@psf.upfronthosting.co.za> <1388165759.72.0.941138301996.issue2550827@psf.upfronthosting.co.za>
In message
 <1388165759.72.0.941138301996.issue2550827@psf.upfronthosting.co.za>
 <1388165759.72.0.941138301996.issue2550827@psf.upfronthosting.co.za>,
 Matt writes:

>Matt added the comment:
>
>Thanks for that link, there is more info there than I appreciated from
>reading the Changes.txt. I see that it does state: "You can run Roundup
>as a Windows service if pywin32_ is installed." in the Optional
>Components Section...

Yes, in doc/installation.txt it does state the pywin32_ requirement.

>I am running python V2.6.6 from http://www.python.org/ and I could start
>the server from the command line...

Good, I don't think you would do that under windows without pywin32_
before the 1.4.21 release.

>Perhaps the changes.txt could be made more explicit?

Yes, I can see where the confusion is. Maybe we can change the two
lines in CHANGES.txt:

  - pywin32 is no longer required to run on Windows (anatoly techtonik)
  - Rewritten portalocker.py logic in ctypes for Windows (anatoly techtonik)

to:

  - Rewritten portalocker.py logic in ctypes for Windows to remove
    dependency on pywin32. Running roundup as a service still needs
    pywin32. (anatoly techtonik)

Anatoly is that acceptable? Do you have other thoughts on how to make
this requirement clearer?
History
Date User Action Args
2013-12-27 17:53:21rouiljsetrecipients: + rouilj, matt109
2013-12-27 17:53:21rouiljlinkissue2550827 messages
2013-12-27 17:53:21rouiljcreate