Custom build of Three.js for SageMath
This package provides a single minified Javascript file three.min.js, which combines
standard Three.js with a number of scripts from examples/jsm/.
The file is made available both as package data of a Python package jupyter_threejs_sage (for local access by SageMath) and as a Jupyter notebook extension (to be installed in the Jupyter notebook's Python environment).
Development
The steps to create this build from a stable tagged version of Three.js are
- Perform a shallow clone of the desired version with
git clone --depth=1 --branch r<n> --single-branch https://github.com/mrdoob/three.js.git
- Add the following lines to
src/Three.jsjust after all other exports
export { OrbitControls } from '../examples/jsm/controls/OrbitControls.js';
export { Line2 } from '../examples/jsm/lines/Line2.js';
export { LineGeometry } from '../examples/jsm/lines/LineGeometry.js';
export { LineMaterial } from '../examples/jsm/lines/LineMaterial.js';
export { LineSegments2 } from '../examples/jsm/lines/LineSegments2.js';
export { LineSegmentsGeometry } from '../examples/jsm/lines/LineSegmentsGeometry.js';
-
Move into the library directory with
cd three.js -
Configure the library with
npm install -
Build the library with
npm run buildThe minified file
three.min.jswill be located in thebuilddirectory. -
Copy the minified file to the
builddirectory here. -
Create a new directory for the new version in
jupyter_threejs_sage/static/and copy the minified file there. (Do not remove old versions that needed by any released versions of Sage.) -
The final step before releasing is to update the
versionfile.
As noted in this issue, Three.js releases can be modified for up to a week after the initial release. This build process should wait for this period of time to ensure future consistency of building.
Metadata
Release files for jupyter-threejs-sage 123
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jupyter-threejs-sage-123.tar.gz | 332.5 kB | Without provenance | Details for jupyter-threejs-sage-123.tar.gz |
Release files / jupyter-threejs-sage-123.tar.gz
| Download URL | jupyter-threejs-sage-123.tar.gz |
|---|---|
| Size | 332.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5657b2784cb8a55663bcd32e602df1c8b9e2d27f35246701b21ba37957db457c
|
|
BLAKE2b-256 checksum How to use checksums |
2930f13204759fdfdaa4449efc7dff72a05413b27c5906420c9c1beb1508b7e4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.24.0 setuptools/49.6.0.post20200917 requests-toolbelt/0.9.1 tqdm/4.50.0 CPython/3.7.6
|
Security for jupyter-threejs-sage 123
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.