jp6/cu126/: polyscope-2.3.0 metadata and description
Polyscope: A viewer and user interface for 3D data.
| author_email | Nicholas Sharp <nmwsharp@gmail.com> |
| classifiers |
|
| description_content_type | text/markdown |
| license | MIT License Copyright (c) 2017-2020 Nicholas Sharp and the Polyscope contributors Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. |
| maintainer_email | Nicholas Sharp <nmwsharp@gmail.com> |
| project_urls |
|
| requires_dist |
|
| requires_python | >=3.7 |
Because this project isn't in the mirror_whitelist,
no releases from root/pypi are included.
| File | Tox results | History |
|---|---|---|
polyscope-2.3.0-cp310-cp310-linux_aarch64.whl
|
|
polyscope-py
Python bindings for Polyscope. https://polyscope.run/py
This library is a python wrapper and deployment system. The core library lives at https://github.com/nmwsharp/polyscope. See documentation at https://polyscope.run/py.
To contribute, check out the instructions here.
Installation
python -m pip install polyscope
or
conda install -c conda-forge polyscope
polyscope-py should work out-of-the-box on any combination of Python 3.7-3.12 and Linux/macOS/Windows. Your graphics hardware must support OpenGL >= 3.3 core profile.
For developers
This repo is configured with CI on github actions.
- By default, all commits to the main branch build & run tests. Use
[ci skip]to skip this. - Tagging a commit with
[ci build]causes it to also build all precompiled wheels on a matrix of platforms to ensure the build scripts succeed. - Tagging a commit with
[ci publish]causes it to build all precompiled wheels on a matrix of platforms AND upload them to pypi index
Deploy a new version
-
Commit the desired version to the
masterbranch. Use the[ci build]string in the commit message to trigger builds, which should take about an hour. -
Watch the github actions builds to ensure all wheels build successfully. The resulting binaries will be saved as artifacts if you want try test with them.
-
While you're waiting, update the docs, including the changelog.
-
Update the version string in
setup.pyto the new version number. When you commit, include the string[ci publish], which will kick of a publish job to build wheels again AND upload them to PyPI. -
If something goes wrong with the build & publish, you can manually retry by pushing any new commit with "[ci publish]" in the message.
-
Create a github release. Tag the release commit with a tag like
v1.2.3, matching the version insetup.py -
Update the conda builds by committing to the feedstock repository. This generally just requires bumping the version number and updating the hash in
meta.yml. Sincemeta.ymlis configured to pull source from PyPi, you can't do this until after the source build has been uploaded from the github action.