Closed kloczek closed 2 years ago
This should be fixed in 7e760728889b3d3928310a453ebe3383adb37984, and I made the test setup use pytest and tox everywhere (51e34d2b8b84f1a582b4dbbfa3693957ddc3f48a, 585373b5d952e579a9f7bd8f6418ca0bfd6a5e35) so hopefully less surprises in the future. Can you test your build against master and if its good I'll release 0.4.26?
Just tested that commit. pytest is no longer failing (Thank you 👍 😄 ) I see however some warnings 😋
Warnings are expected, they are from python-magic to let uses know it's a compatibility layer.
OK .. we can close this ticket or still is on outstanding list? 🤔
Ok I've uploaded 0.4.26, closing.
I'm trying to package your module as an rpm package. So I'm using the typical PEP517 based build, install and test cycle used on building packages from non-root account.
python3 -sBm build -w --no-isolation
build
with--no-isolation
I'm using during all processes only locally installed modulesHere is pytest output:
I'm usimg as input sorce tar bal autogenerated by github from git tag https://github.com/ahupp/python-magic/archive/refs/tags/0.4.25.tar.gz. Those units are failing despite fact that I see in source tree that file