You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i agree with Ian, it's impossible to cover ALL scenrios in a TPI without adopting this in jupyyer extension
if you're plan is to finalize the api based on feedback from jupyter extension adoption, then i don't think we can finalize this api now.
All we (jupyter extension) can do is test this with a simple sample and provide some feedback.
So I talked with the team and decided that we'll finalize it in an iteration or two, hope that gives Jupyter some time to adopt the API. Meanwhile we'll still announce it in our blog posts and release notes to get additional feedback!
Activity
IanMatthewHuff commentedon Sep 27, 2022
Right now I'm testing this with a separate extension as opposed to trying to fully adopt into Jupyter. Seemed like a fairer test of the API itself.
karrtikr commentedon Sep 27, 2022
Yep, by dry-adopting I mean we should make sure it covers all scenarios in the Jupyter extension.
IanMatthewHuff commentedon Sep 27, 2022
That seems a bit much for a single TPI. But so far things all look good with it. Maybe Don knows better if we can just drop this in quickly.
DonJayamanne commentedon Sep 28, 2022
i agree with Ian, it's impossible to cover
ALLscenrios in a TPI without adopting this in jupyyer extensionif you're plan is to finalize the api based on feedback from jupyter extension adoption, then i don't think we can finalize this api now.
All we (jupyter extension) can do is test this with a simple sample and provide some feedback.
we will discuss this in our stand-up.
karrtikr commentedon Sep 28, 2022
I see, in that case just testing and feedback would suffice for purposes of this TPI.
Will discuss with the team on when we plan to finalize it.
karrtikr commentedon Sep 28, 2022
So I talked with the team and decided that we'll finalize it in an iteration or two, hope that gives Jupyter some time to adopt the API. Meanwhile we'll still announce it in our blog posts and release notes to get additional feedback!