OS-dependent paths in configuration files
Bug #145363 reported by
Sidnei da Silva
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Buildout |
Confirmed
|
Wishlist
|
Unassigned |
Bug Description
When putting path values in buildout.cfg for example, it's not clear if one should use '/' or '\' (if on Windows). While using '/' works fine even on Windows, the output of running buildout looks kinda odd because you get a mix of forward and backward slashes. For example, if I say:
"""
[buildout]
....
develop = src/plone.i18n
"""
On the output I get:
"""
Develop: 'C:\\src\
"""
Another example:
"""
extra-paths = C:\src\
"""
Maybe if some key expects a path, it should normalize the slashes to the format expected by the underlying platform.
Changed in zc.buildout: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
To post a comment you must log in.