Skip to content

pandas needs a package-wide config object? #2081

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.

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

Closed
ghost opened this issue Oct 19, 2012 · 2 comments
Closed

pandas needs a package-wide config object? #2081

ghost opened this issue Oct 19, 2012 · 2 comments
Milestone

Comments

@ghost
Copy link

ghost commented Oct 19, 2012

I'm working on the next Unicode PR, which incorporates some global configurables,
and I can't seem to find a convention for handling that uniformly in pandas.

format.py has _GlobalPrintConfig/print_config, and core.api has the corresponding
set_printoptions, It looks to me like they need to be integrated into something more general.

Examples from other projects:

  • matplotlib has rcParams
  • IPython does things differently with config.configurable , but still has a well defined way of
    using/adding configurables.

I suggest a new core.config module to hold all configurables,
It will take over print_config (set_printoptions will keep working),
but will provide a more general namespacing scheme for configurables along with a
getter/setter to be added to core.api.

Once the getter/setter convention is put into place and used uniformly in the code,
the underlying implementation can change as necessary when pandas grows.

if this sounds reasonable, I can follow up with a PR. @wesm?

@wesm
Copy link
Member

wesm commented Oct 20, 2012

This seems perfectly reasonable. I expect there will be more and more configuration options as time goes on.

@ghost
Copy link
Author

ghost commented Dec 11, 2012

closed via 3f6e316

@ghost ghost closed this as completed Dec 11, 2012
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant