Simplify PyScript Offline #2346
Replies: 4 comments 19 replies
-
|
I like this. Especially given some of the folks at PyCon wanted to have a local build of PyScript and one chap struggled to follow the instructions. Perhaps we should use a GitHub action to attach such an asset to the release, and we can link the asset in the auto-generated release web-page (like it already does with the docs, release notes and so on)..? E.g. as an asset attached to something like this: https://github.com/pyscript/pyscript/releases/tag/2025.5.1 and with links on a page like this: https://pyscript.net/releases/2025.5.1/ Just a thought... 👍 |
Beta Was this translation helpful? Give feedback.
-
|
I recently was setting up pyscript to be locally hosted for an app. |
Beta Was this translation helpful? Give feedback.
-
|
I agree with @ntoll that you are describing a release package. That is separaat storage, so wont need to cloned and what have you. In de gh action do the folder assembly and zipping/packing that you need , then add it as an artefact to the release. Pretty sure there actions or gh-cli commands to help |
Beta Was this translation helpful? Give feedback.
-
|
@brettowe @Josverl we've just released 2025.11.2 which includes a pre-built redistributable We're also thinking about providing a way to automatically provide dependencies needed per each package so that it should be trivial to help you out shipping fully redistributable PyScript applications. |
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.
-
We have various ways to obtain files needed to use PyScript offline https://docs.pyscript.net/2025.5.1/user-guide/offline/ and none of these is straight forward.
The current way that doesn't require/need
npmand/or NodeJS to fetch the package is:curl "$(curl -sS https://registry.npmjs.org/@pyscript/core/latest | jq -r .dist.tarball)" --output ./pyscript.tgzAfter that, using untar / gz brings in the
pyscriptfolder with apackageone that contains in it thedistwhich is what any user is after.Issues with all approaches
npmuses semver, not calver, it's very easy to get lost with versions matching in there but also we use that channel for development purposesnpmregistry for distribution purpose doesn't feel right, even if that's the main way most CDNs or projects use itProposal
distinto a new pyscript folderpyscript(TBD ... it could be namedpyscript_coretoo)The current bundle would be ~ 1.5MB all inclusive (as zip) so this should not be an issue but if we think it is, we could also host the artifact in GitHub when we release and point at that specific version ... all to be discussed, I've opened this to discuss indeed and/or have consensus about this way to simplify by far offline installation/use-case.
/cc @ntoll @fpliger @danyeaw
Beta Was this translation helpful? Give feedback.
All reactions