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.

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

move local/panel configurations out of the pyoperant repo #101

Open
neuromusic opened this issue Dec 18, 2015 · 1 comment
Open

move local/panel configurations out of the pyoperant repo #101

neuromusic opened this issue Dec 18, 2015 · 1 comment

Comments

@neuromusic
Copy link
Member

the whole package requires local "panels" to be defined. currently, these are defined in local.py

however, this requires modification of the repo which isn't very helpful for distribution.

instead, I propose that we move any local configuration to a hidden folder in the user's home directory (e.g. /home/user/.pyoperant)

we should see how jupyter, phy, and others do this exactly

@siriuslee
Copy link
Contributor

This would be great. I'm not sure I have any insight yet on what the best way to do this is, but currently I've just added a separate directory to the repo that is only for our lab and will just be keeping an upstream branch updated to this repo's master. That's not a super clean solution, but it does work well when you have custom Behavior classes.

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

2 participants