Using forward-slashes in path for log_file option on win32

[fbrettschneider@…]

As I set via Admin:General:Logging the following logfile name, I got a trac server error. The configuration is: Type=File, Log level=ERROR, Log file=

606/trac.log

The error is:

Internal Server Error

TracError: IOError: [Errno 2] No such file or directory: u'd:\\trac\\myproject\\log\\606/trac.log'

After I manually fixed my trac.ini, Trac worked again. The trac.ini contained this:

[logging]
log_file = 606/trac.log

My system is Bitnami-Trac 0.12.1, Native, Windows

[Remy Blank]

Well, yes, on Windows you have to use backslashes. This shouldn't be surprising.

Did you file a ticket because setting a bad log_file path prevents Trac from working? In that case, it's a duplicate of #8790.

Or was it because you expected forward slashes to be accepted even on Windows? That might be a sensible idea.

[fbrettschneider@…]

I thought Trac doesn't care about slash or backslash. But I could live with it, if Trac didn't stop working. At least Trac should reject the path and tell me the path is wrong. Best case would be Trac can fix the path to backslashes by itself.

[Remy Blank]

Replying to fbrettschneider@…:

Best case would be Trac can fix the path to backslashes by itself.

Ok, let's do that. It can probably be done in PathOption.

[Thijs Triemstra]

Updating ticket summary to reflect request.

[Remy Blank]

On second thought, I find the error message No such file or directory: u'd:\\trac\\myproject\\log\\606/trac.log' explicit enough, and it feels quite logical that you have to use the path separator for the platform running Trac. Modifying Trac to allow '/' everywhere even on Windows would be possible, but then one would expect this to be supported for all path options, including plugins. I don't think it's worth the trouble.

This leaves the "don't stop working" part, which is a duplicate of #8790.