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 skybot into its own "Package" directory #183

Closed
wants to merge 1 commit into from

Conversation

imnotjames
Copy link
Contributor

@imnotjames imnotjames commented Aug 10, 2018

this is suggested for application development, helps us clean up
the project's paths, and assists us in testing because test
frameworks expect this kind of structure!

this also pushes us closer to using plugins from third-party
modules, as plugins can be imported just like any other python
module!

@imnotjames
Copy link
Contributor Author

To follow up with the comment on external plugins - I've been experimenting with a few techniques to pull in plugins from external packages.

However, most of that means it would make a lot of sense to treat the built-in plugins the same way - as modules first, and files to watch for reload second.

this is suggested for application development, helps us clean up
the project's paths, and assists us in testing because test
frameworks expect this kind of structure!

this also pushes us closer to using plugins from third-party
modules, as plugins can be imported just like any other python
module!
@imnotjames imnotjames changed the title move skybot code under its own directory Move skybot into its own "Package" directory Sep 13, 2018
@imnotjames imnotjames closed this Feb 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant