Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve the config loading approach #2

Open
biomadeira opened this issue Sep 1, 2017 · 1 comment
Open

Improve the config loading approach #2

biomadeira opened this issue Sep 1, 2017 · 1 comment
Assignees
@biomadeira
Labels
enhancement

Comments

@biomadeira
Copy link
Collaborator

biomadeira commented Sep 1, 2017 •
edited
Loading

@stuartmac pointed out that loading the new config file to the python module site-packages might lead to some permission errors...

Maybe try a different approach where a .prointvar.config.ini file is written to the users home dir or similar.
@biomadeira biomadeira self-assigned this Sep 1, 2017
@stuartmac
Copy link
Member

I'd also suggest considering a hierarchical check for config files. Like,

  1. Working directory
  2. Home directory
  3. Install directory

That would let you override the installed config without having to run ProIntVar-Core-config-load before and after (if you wanted to revert)...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@biomadeira biomadeira

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@biomadeira @stuartmac