This release is a pre-release and may not be stable for production use.
# Custom build of Three.js for SageMath
The steps to create this build from a stable tagged version 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.js just 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 build
The minified file will be located in the build directory and has been copied to the same directory here. The final step before releasing is to update the version file with the new number.
As noted in [this issue](https://github.com/mrdoob/three.js/issues/20591), 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 122b1
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-122b1.tar.gz | 167.2 kB | Without provenance | Details for jupyter-threejs-sage-122b1.tar.gz |
Release files / jupyter-threejs-sage-122b1.tar.gz
| Download URL | jupyter-threejs-sage-122b1.tar.gz |
|---|---|
| Size | 167.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46cd4fb3ccebbd0c8fb496da065765c7e71c2a83c7d9e39c31ee95aff3e18714
|
|
BLAKE2b-256 checksum How to use checksums |
a7a9eab448eeca503d3615b13de50fc938f0239a6d48cd1028bca47ed214fd8d
|
| 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 122b1
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.
