zope.configuration.fields.Path doesn't handle home directories

[Bert Vanderbauwhede]

The fieldtype Path from zope.configuration.fields doesn't handle home directories, indicated by a ~ in the path. The path ~/some.file will be interpreted as /path/to/some/package/~/some.file, while it should be something like /home/someuser/some.file.

[Fred Drake (fdrake)]

How much need is there for ~/some.file or ~user/some.file in ZCML?

If you're not using this from ZCML, could you describe you use case?

[Bert Vanderbauwhede (batlock666)]

On Wed, Dec 9, 2009 at 2:44 PM, Fred Drake <email address hidden> wrote:

> How much need is there for ~/some.file or ~user/some.file in ZCML?
>
> If you're not using this from ZCML, could you describe you use case?
>
>
I use it in a custom ZCML-directive. The directive defines a
configuration-file in INI-format. The handler for the directive reads the
file, and makes the contents available in a global utility:

In ZCML, I define:

<ugent:configurationFile path="~/some.config.ini"
                         name="some_config" />

Then in Zope, I can do this:

>>> config = getUtility(IConfigurationFile, name="some_config")
>>> config.getSections()
['some_section', 'some_other_section']

I use this to define connection-settings for MySQL and LDAP.

--
Bert Vanderbauwhede

[Tres Seaver (tseaver)]

Please follow up on Github:

  https://github.com/zopefoundation/zope.configuration/issues/3