trouble repackaging package it as rpm and IPS packages. about pytest-check HOT 12 CLOSED

OK so where is the issue? :P

from pytest-check.

OK so where is the issue? :P

Ain't no issue for me anymore. Thanks for the module - very helpful.

from pytest-check.

Wondering whether https://api.travis-ci.com/v3/job/528047688/log.txt is another example of this where 'xfailed_key' fails to import. This was with python 3.6.

from pytest-check.

Wondering whether https://api.travis-ci.com/v3/job/528047688/log.txt is another example of this where 'xfailed_key' fails to import. This was with python 3.6.

Answering my own follow-up: this is Travis using built-in pytest which is easily fixed by moving to latest pytest in the install steps of the virtual env.

from pytest-check.

Currently passing CI : https://github.com/okken/pytest-check/actions/workflows/main.yml
If you are changing your PYTHONPATH, maybe don't do that?

from pytest-check.

changed the summary to "trouble setting up dev environment".
Does that capture the problem ok?

from pytest-check.

Not at all.
Still have problems with uderstanding what you want to tell :/
May I sask what is wromg with that procedure which I've described on top of this ticket?

from pytest-check.

If you want to use pytest-check, just install it: pip install pytest-check

If you want to clone it and run the tests:

$ git clone https://github.com/okken/pytest-check.git
$ cd pytest-check 
$ python3 -m venv venv          
$ source venv/bin/activate
(venv) $ pip install tox
(venv) $ tox   
... lots of tox output ...
____________________________________________ summary _____________________________________________
  py37: commands succeeded
  py38: commands succeeded
  py39: commands succeeded
  py310: commands succeeded
  coverage: commands succeeded
  flake8: commands succeeded
  congratulations :)

If you want to run tests directly, without tox:

(venv) $ pip install flit pytest
(venv) $ flit install
(venv) $ pytest
====================================== test session starts =======================================
collected 38 items                                                                               

tests/test_check.py .........................                                              [ 65%]
tests/test_check_context_manager.py ......                                                 [ 81%]
tests/test_check_errors.py ...                                                             [ 89%]
tests/test_check_fixture.py .                                                              [ 92%]
tests/test_check_func_decorator.py ...                                                     [100%]

======================================= 38 passed in 1.03s =======================================

There is no use of setup.py in this project.
There is no need to modify PYTHONPATH or PATH, either to run tests or to use pytest-check.

Are you using trying to use pytest-check? or run the tests for it?
Are you trying to do any of that outside of a virtual environment?

Is there something you think is broken in pytest-check?
Or are you asking for help with your particular use case?

from pytest-check.

There is no use of setup.py in this project.
There is no need to modify PYTHONPATH or PATH, either to run tests or to use pytest-check.

OK I think that I need to drop some context 😀
I'm not building/installing pytest-check to use it with $PYTHINPATH but to package it as rpm and IPS packages.
That procedure which I've described is used typically on such packaging processes.
tox indeed passes without errors but still issue remains why pytest with all those extensions which are listed on top is failing with some errors which suggests that it is not something related to testing methodology🤔

In this case I've opened the ticket only because errors produced by non-pure pytest may point on some real issues with tested code .. or issues with those extensions.
Only this and nothing more 😀
On building my packages I'm using spawned to build only one package lxc zones or Solaris zones (in case of Solaris) with installed only build dependencies however before send ready to build package to the furnace I'm usually trying to perform some additional tests in env with installed all possible pytest extensions to see what pytest produces .. and above output is from such build "rich" build env 😀

Automatically generated setup.py is in sdist tar ball downloaded from pypi.
I'm using setuptools on build and install procedure because it is still easiest way to do what needs to be done on typical packaging process.
However if you know how alter my template procedure and do the same without using setuptools I'll be really appreciated 😀

I think that above may fill few gaps in the context which indeed is not obvious (I should apologise for dropping just output without few additional bits .. so I'm doing that 🙇‍♂️).
Nevertheless question why in this case pytest point on some issues still remains ..🤔🥺

from pytest-check.

Ok. That makes more sense.
However, I have no idea how to help you.
I've reached out to a couple of people.
I'll let you know if I find anything out.

This isn't going to be a problem with just this package, as I'm not doing anything super crazy here, just using flit for packaging.

from pytest-check.

I guess I'd recommend trying to just use the wheel instead of the tar.gz if there is a wheel.

from pytest-check.

use flit or py py/build

from pytest-check.