Skip to content
This repository has been archived by the owner on Mar 29, 2024. It is now read-only.

+include ... should be relative to the "source file", not the current working dir of the executable #88

Closed
peterbe opened this issue Sep 5, 2013 · 4 comments

Comments

@peterbe
Copy link
Contributor

peterbe commented Sep 5, 2013

If you do cd /some/place; python some_app.py --admin.conf=/tmp/some.ini and some.ini contains the line

+include other_file.ini

it should then look for /tmp/other_file.ini NOT /some/place/other_file.ini

@GabiThume
Copy link
Contributor

I am not sure at all that this can be solve the issue: GabiThume@ae388a5#commitcomment-4029289, but I created a test and it worked!

@peterbe
Copy link
Contributor Author

peterbe commented Sep 6, 2013

Merge in my demo app into it and then make a pull request and I'll land it.

@twobraids
Copy link
Contributor

is this issue resolved?

and, by the way, it did do the proper relative behavior if you specify the path like this:

+include ./relative/path/to/something.ini

@peterbe
Copy link
Contributor Author

peterbe commented Nov 11, 2013

Done in beefb25

It now works with +include ./some/path.ini and +include some/path.ini and +include /some/path.ini

@peterbe peterbe closed this as completed Nov 11, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants