Sure. $ virtualenv /tmp/svgpathtest $ /tmp/svgpathtest/bin/python setup.py sdist $ /tmp/svgpathtest/bin/pip install dist/svg.path-4.0.tar.gz $ /tmp/svgpathtest/bin/python
import svg Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named svg
I attached a full log, plus the failing package file. On Sun, Nov 3, 2019 at 7:02 PM Alex Grönholm <alex.gronholm@nextday.fi> wrote:
I was unable to reproduce the issues you're seeing. Could you give detailed repro instructions?
Lennart Regebro kirjoitti 3.11.2019 klo 17.46:
Heya!
I recently moved all the setup.py configuration into setup.cfg for Pyroma. That worked very nicely. So I started doing it for my other packages, but with svn.path I failed. Everything *looked* fine, and I uploaded a 4.0 to PyPI, but if I install that in a virtualenv, importing svg or svg.path fails. The Python installation can't find them. Declaring them as a namespace means you can import them, but the imports are empty, there is no attributes to the modules, so you still can't use the package.
Is this possible? And if so, how?
Here's a link to the 4.0 release with all the info in the setup.cfg. https://github.com/regebro/svg.path/tree/5f941b729f0b7e3991f238776c9391d5791... -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/XQJAO... -- Distutils-SIG mailing list -- distutils-sig@python.org To unsubscribe send an email to distutils-sig-leave@python.org https://mail.python.org/mailman3/lists/distutils-sig.python.org/ Message archived at https://mail.python.org/archives/list/distutils-sig@python.org/message/SMEYW...