Replies: 2 comments 9 replies
-
|
Beta Was this translation helpful? Give feedback.
-
|
I'd like to remind that synclink stuff is nowhere published in the release so this task feels like ... let's just remove pyscriptjs folder and call it a day. We don't use anything from legacy code so synclink is not affecting by any mean the 2023 release to me, unless there's something else I am not considering. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah. This is more about removing the old code (which includes old usage of synclink) |
Beta Was this translation helpful? Give feedback.
-
|
AFAIK this has been done so @madhur-tandon do you mind checking that box? ;-) |
Beta Was this translation helpful? Give feedback.
-
|
Done |
Beta Was this translation helpful? Give feedback.
-
|
I opened two issues to keep track of the tests which are currently skipped.
I think we should try to fix all the main thread tests, to have feature-parity with classic. For workers, we said that it's not necessary to have feature-parity so in theory we could decide to do the release even if some functionality is still missing. However, I think we should at least try to fix them, because they are related to very important features (error messages and |
Beta Was this translation helpful? Give feedback.
-
|
what's the issue with |
Beta Was this translation helpful? Give feedback.
-
|
also, about this:
we want as much backward compatibility as possible but I think 1:1 feature-parity with classic should not even be a goal ... otherwise we should've just kept working on classic instead, right? We have new features, new patterns, new API, and that's the reason we're releasing PyScript Next ... not PyScript like before but also with other stuff ... the latter is a bit late in the pipe to me, not sure we're aligned in here. |
Beta Was this translation helpful? Give feedback.
-
|
Whether we strive for 1:1 feature-parity or not, that Epic is a good chance for us as a group to go through the features from Classic that are not-yet-implemented Next, and ask "Do we want to include this in a release, or not?" Even if each implementation not 100% identical, we can ask "Do we want error/warning banners? Do we want to reintroduce |
Beta Was this translation helpful? Give feedback.
-
|
sure thing, I didn't want to dismiss by any mean @antocuni work on this, he's been super helpful in general around various other topics too, I was just thinking if the goal for 2023 is to release Do we want to focus on that? If that's the case, the punchlist becomes pretty meaningless to me, as there's way more to discuss and/or implement and/or fix, I hope this clarifies my previous message. |
Beta Was this translation helpful? Give feedback.
-
|
What I think I've been hearing so far from almost all maintainers is the same thing in different flavors. Basically, instead of Honestly, personally, I wouldn't like to go and re-create a massive list that will take another month for us to close.... I'd much rather build that list, pick what can solidify the release and small additional features (for instance, |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The goal of this discussion is to set a clear target for the 2023 Release. Given that #1653 is basically done, here's the list of pending features and tasks for us to complete the release:
Beta Was this translation helpful? Give feedback.
All reactions