testenv | A collection of web pages vulnerable to SQL injection flaws | SQL Database library

tox does not care about a conftest.py, as this is configuration/collection file for pytest fixtures.

Adding or removing skipdist from or to a tox.ini file does not make a difference, as this is no valid tox setting. I think you meant skipsdist, see https://tox.wiki/en/latest/config.html

You probably want to delete the __init__.py in your src directory - this is meant to be a folder with only your project source in it, ie the one folder. src should not be importable.

The specific problem with your setup is, that you install the project with tox, but then use a Python interpreter (C:\Program Files\Autodesk\Maya2022\bin\mayapy) which has no access to the installed package - that is why you get the ModuleNotFoundError.

The reason why from src.one.module_one import create_sphere works - at least a bit - is that you invoke pytest as a module.

python -m pytest makes pytest add the current dir to sys path, see https://jugmac00.github.io/til/what-is-the-difference-between-invoking-pytest-and-python-m-pytest/

So, how to fix this?

In general and as far as I know tox is not meant to work with custom interpreters.

Maybe you can work around that by manipulating sys.path by adding the one directory to the path, which is then available to your custom interpreter.

This means that your project needs to work without being installed, and the tests need to be discoverable from the "external" pytest.

I cannot determine whether these workarounds are useful and work for you, as I am not familiar with Maya, but I am one of the tox developers and what you do is definitely not "maintstream" :-)

P.S.: You could also use the install_command to install your package not with pip from your tox env, but with pip from Maya, see https://tox.wiki/en/latest/config.html#conf-install_command and https://knowledge.autodesk.com/support/maya/downloads/caas/CloudHelp/cloudhelp/2022/ENU/Maya-Scripting/files/GUID-72A245EC-CDB4-46AB-BEE0-4BBBF9791627-htm.html

Maybe something like that:

As stated in the comment, the fix was to add a merchantId to the Stripe initialization

I found the answer myself. The problem was that requirements.txt was not included by my 'MANIFEST.in' file. I changet the file to:

You could negate a regex pattern for the TOX_SKIP_ENV as the following:

You need to mark those "Marshmellow" tests with a pytest marker.

https://docs.pytest.org/en/6.2.x/example/markers.html

e.g.

Looks like this is what happened:

1. Your code invoked presentPaymentSheet.
2. It internally invoked flowController?.presentPaymentOptions.
3. It checked and found FlowController wasn't properly initialized and emit that error.

The reason FlowController is not properly initialized is because there was null or empty client secret passed in. You would want to check if your clientSecret variable from navigateToCheckout actually had a value.

You can use the change event of the Kendo Grid to get the selected row. See the snippet below for a demo from the Kendo documentation.

this was a bug in setuptools which has already been fixed (see also the pinned issue on isort)

you can work around this bug by setting the following environment variable: SETUPTOOLS_USE_DISTUTILS=stdlib

the version of setuptools comes from the version of virtualenv you're using, so you may want to upgrade to get the correct version

here's a longer summary of what went wrong with setuptools:

here's the relevant things to follow up on:

• https://github.com/pypa/setuptools/issues/2353
• https://github.com/pypa/pip/issues/6264
• https://github.com/pypa/setuptools/issues/2980

why we're suddenly seeing this:

• the latest virtualenv release upgraded setuptools to 60.1.0 (despite what the changelog says it was upgraded to 60.1.0 here)
• setuptools 60.* changes the default to using the setuptools-embedded distutils rather than the stdlib distutils
• setuptools does this by way of a .pth file which redirects imports of distutils to setuptools._distutils
• during pip's isolated builds (triggered by pyproject.toml, for example to install isort via poetry) pip attempts to clear the current sys.path of the enclosing environment and isolates to the pyproject.toml-installed build dependencies, but it's a bit too late as the .pth files from the enclosing environment are applied. so in this environment setuptools is not installed, but its import hooks are

disclaimer: I created pre-commit