Many potential users of jupyterlite are likely to consider themselves "notebook users" rather than developers. This template repo helps provide an on-ramp to unexperienced users with a way to get started with their own deployment of jupyterlite, as well as exploring what's possible via the demo notebooks.
Such users might be consider themselves "notebook users" rather than developers and might be frustrated if things they expect to work don't (yet) work.
It might be useful to have a notebook of "not yet working" examples of things that folk are likely to try but that don't yet work, with workarounds if available, perhaps with a brief explanation of why they don't (yet) work.
Problem
Many potential users of
jupyterlite
are likely to consider themselves "notebook users" rather than developers. This template repo helps provide an on-ramp to unexperienced users with a way to get started with their own deployment ofjupyterlite
, as well as exploring what's possible via the demo notebooks.Such users might be consider themselves "notebook users" rather than developers and might be frustrated if things they expect to work don't (yet) work.
It might be useful to have a notebook of "not yet working" examples of things that folk are likely to try but that don't yet work, with workarounds if available, perhaps with a brief explanation of why they don't (yet) work.
See also: https://github.com/jupyterlite/jupyterlite/issues/199
Suggested Improvement
Create a notebook with a set of "not yet working" items.
For example:
%pip
not available [related issue]pd.read_csv()
file not found;sqliite
file not found etc. [related issue]