Release as Python 3 source wheel on PyPI?
See original GitHub issueIt seems one could install pyshp on Pyodide and hence JupyterLite using micropip if it would have a source wheel package on PyPI. Maybe worth a thought?
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Packaging and distributing projects
Source distributions. Wheels. Pure Python Wheels. Platform Wheels ... Versions are displayed on PyPI for each release if you publish your project.
Read more >wheel - PyPI
A built-package format for Python. ... Released: Nov 9, 2022 ... This library is the reference implementation of the Python wheel packaging standard, ......
Read more >How to install, download and build Python wheels - ActiveState
This will create both a source distribution (sdist) and a wheel file (bdist_wheel) , along with all of its dependencies. You can now...
Read more >Release as Python 3 source wheel on PyPI? · Issue #56 ... - GitHub
It seems one could install pycrs on Pyodide and hence JupyterLite using micropip if it would have a source wheel package on PyPI....
Read more >How to Publish an Open-Source Python Package to PyPI
PEP 427 describes how wheels should be packaged. PEP 440 describes how version numbers should be parsed. PEP 508 describes how dependencies ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@alexandreCameron i would definitely suggest an upgrade from v1.2.3 to 2.1.3, as there have been plenty of bug fixes, performance improvements, and new features. However, the python 2 artifacts you are referring to (unicode, basestring, etc) are inside an if-clause that only gets triggered if the version is python 2. As indicated in the project readme, pyshp continues to support and run smoothly for both python 2.7 and 3+, backed up by doctests and unittest. So if you’re having problems when upgrading to a later version, i suspect the errors are rather due to backwards incompatible changes after the major version bump to v2. I’m adding more details in the openquake issue thread you referenced.
@deeplook v2.2.0 is now out on pypi with a source wheel (‘pyshp-2.2.0-py3-none-any.whl’). Does this fix the issue for pyodide/jupyterlite/micropip?