-
Notifications
You must be signed in to change notification settings - Fork 363
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
Split Python and JavaScript packages #1168
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me so far! Thanks!
FYI @maartenbreddels |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice, also @mariobuikhuizen might be interested in this.
Note that we can still have a ipyleaflet-core pypi package installing a python ipyleaflet package, and the metapackage (ipyleaflet) doesn't need to install any code.
In my experience the from ipyleaflet_core import *
doesn't work that nicely in practice. It will also break from ipyleaflet.<somemodule> import SomeClass
.
Great and brave work ! 👍
Indeed we were wondering about this yesterday.
Good point indeed! We should definitely do that then. |
Nice, and here you only installed ipyleaflet-core? |
Indeed. We should install the metapackage there too. |
861be2b
to
35c9a59
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Split package into separate front end and back end packages based on #1163