Comments (7)
RKrahl
commented on June 19, 2024
I have no idea what you were trying to do. I'd need more information in order to give a somewhat useful answer.
$ tar xfz pytest-dependency-0.6.0.tar.gz
$ cd pytest-dependency-0.6.0
$ python3.8 -sBm build -w --no-isolation
* Getting build dependencies for wheel...
running egg_info
creating src/pytest_dependency.egg-info
writing src/pytest_dependency.egg-info/PKG-INFO
writing dependency_links to src/pytest_dependency.egg-info/dependency_links.txt
writing entry points to src/pytest_dependency.egg-info/entry_points.txt
writing requirements to src/pytest_dependency.egg-info/requires.txt
writing top-level names to src/pytest_dependency.egg-info/top_level.txt
writing manifest file 'src/pytest_dependency.egg-info/SOURCES.txt'
adding license file 'LICENSE.txt' (matched pattern 'LICEN[CS]E*')
reading manifest file 'src/pytest_dependency.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'src/pytest_dependency.egg-info/SOURCES.txt'
* Building wheel...
running bdist_wheel
running build
running build_py
running meta
version: 0.6.0
creating build
creating build/lib
copying (with substitutions) src/pytest_dependency.py -> build/lib
installing to build/bdist.linux-x86_64/wheel
running install
running install_lib
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/wheel
copying build/lib/pytest_dependency.py -> build/bdist.linux-x86_64/wheel
running install_egg_info
running egg_info
writing src/pytest_dependency.egg-info/PKG-INFO
writing dependency_links to src/pytest_dependency.egg-info/dependency_links.txt
writing entry points to src/pytest_dependency.egg-info/entry_points.txt
writing requirements to src/pytest_dependency.egg-info/requires.txt
writing top-level names to src/pytest_dependency.egg-info/top_level.txt
adding license file 'LICENSE.txt' (matched pattern 'LICEN[CS]E*')
reading manifest file 'src/pytest_dependency.egg-info/SOURCES.txt'
reading manifest template 'MANIFEST.in'
writing manifest file 'src/pytest_dependency.egg-info/SOURCES.txt'
Copying src/pytest_dependency.egg-info to build/bdist.linux-x86_64/wheel/pytest_dependency-0.6.0-py3.8.egg-info
running install_scripts
adding license file "LICENSE.txt" (matched pattern "LICEN[CS]E*")
creating build/bdist.linux-x86_64/wheel/pytest_dependency-0.6.0.dist-info/WHEEL
creating '/home/abuild/test/pytest-dependency-0.6.0/dist/tmp8lwczho7/pytest_dependency-0.6.0-py3-none-any.whl' and adding 'build/bdist.linux-x86_64/wheel' to it
adding 'pytest_dependency.py'
adding 'pytest_dependency-0.6.0.dist-info/LICENSE.txt'
adding 'pytest_dependency-0.6.0.dist-info/METADATA'
adding 'pytest_dependency-0.6.0.dist-info/WHEEL'
adding 'pytest_dependency-0.6.0.dist-info/entry_points.txt'
adding 'pytest_dependency-0.6.0.dist-info/top_level.txt'
adding 'pytest_dependency-0.6.0.dist-info/RECORD'
removing build/bdist.linux-x86_64/wheel
Successfully built pytest_dependency-0.6.0-py3-none-any.whl
Works for me.
In any case:
- Please check out the Installation instructions for pytest-dependency.
- whatever you want to do to install pytest-dependency, always start from the released source distribution.
from pytest-dependency.
kloczek
commented on June 19, 2024
Did you try to use autogenerated from git tag tar ball? 🤔
from pytest-dependency.
RKrahl
commented on June 19, 2024
I did exactly what I wrote above: I unpacked the source distribution changed into that directory and ran python3.8 -sBm build -w --no-isolation. (You need to have build and wheel installed for this command to work.)
You still didn't tell me what you were trying to do. I suspect that you didn't start from the source distribution, but from the cloned git repository. In that case, you'd need to additionally install git-props (and the git program of course).
from pytest-dependency.
kloczek
commented on June 19, 2024
I did exactly what I wrote above: I unpacked the source distribution changed into that directory and ran python3.8 -sBm build -w --no-isolation. (You need to have build and wheel installed for this command to work.)
Do you have git matadata in that tar ball?
Autogenerated from git tag tar ball has no .git/directory.
BTW: why not use for example setuptool-scm instead setuptools + set of custom reads from git metadata? 🤔
It would allow as well significantly shorten setup.py.
from pytest-dependency.
kloczek
commented on June 19, 2024
BTW:
Lines 10 to 13 in 9d5e0d3
distutils is already deprecated.from pytest-dependency.
kloczek
commented on June 19, 2024
Next thing
Line 162 in 9d5e0d3
Looks like
setuptools can be removed from that list.from pytest-dependency.
RKrahl
commented on June 19, 2024
In my very first comment above, I pointed you to the Installation instructions for pytest-dependency. May I suggest you to actually read that piece of documentation?
Do you have git matadata in that tar ball? Autogenerated from git tag tar ball has no .git/directory.
That tar ball is the source distribution that is supposed to be the starting point for any attempt to install pytest-dependency. And yes, it contains the relevant metadata.
BTW: why not use for example
setuptool-scminsteadsetuptools+ set of custom reads from git metadata? 🤔
I use git-props instead of setuptool-scm. It is similar, but has some advantages over the latter.
It would allow as well significantly shorten setup.py.
Bullshit!
distutils is already deprecated.
It was deprecated in the standard library and has been removed from there in Python 3.12. But it is still included in setuptools, actually, it is the basis that setuptools builds upon.
Looks like
setuptoolscan be removed from that list.
It is required for the manual installation from the source distribution.
I repeat myself: you still didn't tell me what you were trying to do. You didn't provided any reproducible error description. I thus close as invalid.
from pytest-dependency.
Related Issues (20)
- Test suite incompatibility with pytest 6.2 HOT 2
- Tests skipped on linux(3.6.13)(with no test failed) but executing on windows(3.6.10) HOT 3
- Dependency between two tests HOT 1
- session scope not working HOT 1
- Depends on all test methods in class HOT 1
- Conditional dependency on 2 tests HOT 2
- 0.5.1: pytest is failing HOT 4
- Is ordering on fixtures supported?
- only test_b is passed when install pytest-xdist with n>2.
- Not skipping a test when parent test skips or xfails
- The test was skipped,although the dependency test is success. HOT 5
- Dependency call is skipped by executing test with mark HOT 3
- pytest dependency not skipping the dependent tests when failed HOT 3
- when the dependency case use @pytest.mark.parametrize, depened cases was skipped,although the dependency test is success HOT 1
- is @pytest.mark.dependency() can be used for class level? like API test class depends on BVT test class...
- pyproject.toml missing
- Inheriting from test class with dependencies doesn't work correctly HOT 1
- Is pytest-dependency suppose to tell me why a test was skipped? I see nothing in the output explaining why. HOT 1
- Rerunning skipped cases when the parent test fails HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pytest-dependency.