Overview

Request 642677 accepted

- specfile:
* require filelock
* CHANGELOG.rst ->changelog.rst, added CONTRIBUTORS CONTRIBUTING.rst to doc
* add fdupes
- update to version 3.5.2:
* Bugfixes
+ session packages are now put inside a numbered directory
(instead of prefix numbering it, because pip fails when wheels
are not named according to `PEP-491
`_, and prefix
numbering messes with this) - by :user:`gaborbernat` (`#1042
`_)
* Features
+ level three verbosity ("-vvv") show the packaging output - by
:user:`gaborbernat` (`#1047
`_)
- changes from version 3.5.1:
* Bugfixes
+ fix regression with "3.5.0": specifying "--installpkg" raises
"AttributeError: 'str' object has no attribute 'basename'"
(`#1042 `_)
- changes from version 3.5.0:
* Bugfixes
+ intermittent failures with "--parallel--safe-build", instead of
mangling with the file paths now uses a lock to make the package
build operation thread safe and is now on by default
("--parallel--safe-build" is now deprecated) - by
:user:`gaborbernat` (`#1026
`_)
* Features
+ Added "temp_dir" folder configuration (defaults to
"{toxworkdir}/.tmp") that contains tox temporary files. Package
builds now create a hard link (if possible, otherwise copy -
notably in case of Windows Python 2.7) to the built file, and
feed that file downstream (e.g. for pip to install it). The hard
link is removed at the end of the run (what it points though is
kept inside "distdir"). This ensures that a tox session operates
on the same package it built, even if a parallel tox run builds
another version. Note "distdir" will contain only the last built
package in such cases. - by :user:`gaborbernat` (`#1026
`_)
* Documentation
+ document tox environment recreate rules (:ref:`recreate`) - by
:user:`gaborbernat` (`#93
`_)
+ document inside the "--help" how to disable colorized output via
the "PY_COLORS" operating system environment variable - by
:user:`gaborbernat` (`#163
`_)
+ document all global tox flags and a more concise format to
express default and type - by :user:`gaborbernat` (`#683
`_)
+ document command line interface under the config section `cli
`_
- by :user:`gaborbernat` (`#829
`_)
- changes from version 3.4.0:
* Bugfixes
+ add "--exists-action w" to default pip flags to handle better
VCS dependencies (`pip documentation on this
`_)
- by :user:`gaborbernat` (`#503
`_)
+ instead of assuming the Python version from the base python name
ask the interpreter to reveal the version for the
"ignore_basepython_conflict" flag - by :user:`gaborbernat`
(`#908 `_)
+ PEP-517 packaging fails with sdist already exists, fixed via
ensuring the dist folder is empty before invoking the backend
and `pypa/setuptools 1481
`_ - by
:user:`gaborbernat` (`#1003
`_)
* Features
+ add "commands_pre" and "commands_post" that run before and after
running the "commands" (setup runs always, commands only if
setup suceeds, teardown always - all run until the first failing
command) - by :user:`gaborbernat` (`#167
`_)
+ "pyproject.toml" config support initially by just inline the
tox.ini under "tool.tox.legacy_tox_ini" key; config source
priority order is "pyproject.toml", "tox.ini" and then
"setup.cfg" - by :user:`gaborbernat` (`#814
`_)
+ use the os environment variable "TOX_SKIP_ENV" to filter out tox
environment names from the run list (set by "envlist") - by
:user:`gaborbernat` (`#824
`_)
+ always set "PIP_USER=0" (do not install into the user site
package, but inside the virtual environment created) and
"PIP_NO_DEPS=0" (installing without dependencies can cause
broken package installations) inside tox - by
:user:`gaborbernat` (`#838
`_)
+ tox will inject some environment variables that to indicate a
command is running within tox: "TOX_WORK_DIR" env var is set to
the tox work directory, "TOX_ENV_NAME" is set to the current
running tox environment name, "TOX_ENV_DIR" is set to the
current tox environments working dir - by :user:`gaborbernat`
(`#847 `_)
+ While running tox invokes various commands (such as building the
package, pip installing dependencies and so on), these were
printed in case they failed as Python arrays. Changed the
representation to a shell command, allowing the users to quickly
replicate/debug the failure on their own - by
:user:`gaborbernat` (`#851
`_)
+ skip missing interpreters value from the config file can now be
overridden via the "--skip-missing-interpreters" cli flag - by
:user:`gaborbernat` (`#903
`_)
+ keep additional environments config order when listing them - by
:user:`gaborbernat` (`#921
`_)
+ allow injecting config value inside the ini file dependent of
the fact that we're connected to an interactive shell or not -
by :user:`gaborbernat` (`#947
`_)
+ do not build sdist if skip install is specified for the envs to
be run - by :user:`gaborbernat` (`#974
`_)
+ when verbosity level increases above two start passing through
verbosity flags to pip - by :user:`gaborbernat` (`#982
`_)
+ when discovering the interpreter to use check if the tox host
Python matches and use that if so - by :user:`gaborbernat`
(`#994 `_)
+ "-vv" will print out why a virtual environment is re-created
whenever this operation is triggered - by :user:`gaborbernat`
(`#1004 `_)
* Documentation
+ clarify that "python" and "pip" refer to the virtual
environments executable - by :user:`gaborbernat` (`#305
`_)
+ add Sphinx and mkdocs example of generating documentation via
tox - by :user:`gaborbernat` (`#374
`_)
+ specify that "setup.cfg" tox configuration needs to be inside
the "tox:tox" namespace - by :user:`gaborbernat` (`#545
`_)

Loading...

Tomáš Chvátal's avatar

Seems you removed six runtime dependency requires, that sounds wrong. Also the filelock might be also needed on runtime no?


Matej Cepl's avatar

Also, add %fdupes %{buildroot}%{_prefix}%{$python_sitelib} to the end of %install (and fdupes to BuildRequires).


Tomáš Chvátal's avatar

%python_expand %fdupes %{buildroot}%{$python_sitelib}


Arun Persaud's avatar
author source maintainer

working on the changes...

Strange about the six-requirement since I still have a line with the requirement on my local computer? Anyway, will fix (hopefully) and submit again.

I also don't understand the comment about the tests. It seems to me that the tests are run automatically and I only submitted after I got a successful build, so the test must have passed?

Request History
Arun Persaud's avatar

apersaud created request

- specfile:
* require filelock
* CHANGELOG.rst ->changelog.rst, added CONTRIBUTORS CONTRIBUTING.rst to doc
* add fdupes
- update to version 3.5.2:
* Bugfixes
+ session packages are now put inside a numbered directory
(instead of prefix numbering it, because pip fails when wheels
are not named according to `PEP-491
`_, and prefix
numbering messes with this) - by :user:`gaborbernat` (`#1042
`_)
* Features
+ level three verbosity ("-vvv") show the packaging output - by
:user:`gaborbernat` (`#1047
`_)
- changes from version 3.5.1:
* Bugfixes
+ fix regression with "3.5.0": specifying "--installpkg" raises
"AttributeError: 'str' object has no attribute 'basename'"
(`#1042 `_)
- changes from version 3.5.0:
* Bugfixes
+ intermittent failures with "--parallel--safe-build", instead of
mangling with the file paths now uses a lock to make the package
build operation thread safe and is now on by default
("--parallel--safe-build" is now deprecated) - by
:user:`gaborbernat` (`#1026
`_)
* Features
+ Added "temp_dir" folder configuration (defaults to
"{toxworkdir}/.tmp") that contains tox temporary files. Package
builds now create a hard link (if possible, otherwise copy -
notably in case of Windows Python 2.7) to the built file, and
feed that file downstream (e.g. for pip to install it). The hard
link is removed at the end of the run (what it points though is
kept inside "distdir"). This ensures that a tox session operates
on the same package it built, even if a parallel tox run builds
another version. Note "distdir" will contain only the last built
package in such cases. - by :user:`gaborbernat` (`#1026
`_)
* Documentation
+ document tox environment recreate rules (:ref:`recreate`) - by
:user:`gaborbernat` (`#93
`_)
+ document inside the "--help" how to disable colorized output via
the "PY_COLORS" operating system environment variable - by
:user:`gaborbernat` (`#163
`_)
+ document all global tox flags and a more concise format to
express default and type - by :user:`gaborbernat` (`#683
`_)
+ document command line interface under the config section `cli
`_
- by :user:`gaborbernat` (`#829
`_)
- changes from version 3.4.0:
* Bugfixes
+ add "--exists-action w" to default pip flags to handle better
VCS dependencies (`pip documentation on this
`_)
- by :user:`gaborbernat` (`#503
`_)
+ instead of assuming the Python version from the base python name
ask the interpreter to reveal the version for the
"ignore_basepython_conflict" flag - by :user:`gaborbernat`
(`#908 `_)
+ PEP-517 packaging fails with sdist already exists, fixed via
ensuring the dist folder is empty before invoking the backend
and `pypa/setuptools 1481
`_ - by
:user:`gaborbernat` (`#1003
`_)
* Features
+ add "commands_pre" and "commands_post" that run before and after
running the "commands" (setup runs always, commands only if
setup suceeds, teardown always - all run until the first failing
command) - by :user:`gaborbernat` (`#167
`_)
+ "pyproject.toml" config support initially by just inline the
tox.ini under "tool.tox.legacy_tox_ini" key; config source
priority order is "pyproject.toml", "tox.ini" and then
"setup.cfg" - by :user:`gaborbernat` (`#814
`_)
+ use the os environment variable "TOX_SKIP_ENV" to filter out tox
environment names from the run list (set by "envlist") - by
:user:`gaborbernat` (`#824
`_)
+ always set "PIP_USER=0" (do not install into the user site
package, but inside the virtual environment created) and
"PIP_NO_DEPS=0" (installing without dependencies can cause
broken package installations) inside tox - by
:user:`gaborbernat` (`#838
`_)
+ tox will inject some environment variables that to indicate a
command is running within tox: "TOX_WORK_DIR" env var is set to
the tox work directory, "TOX_ENV_NAME" is set to the current
running tox environment name, "TOX_ENV_DIR" is set to the
current tox environments working dir - by :user:`gaborbernat`
(`#847 `_)
+ While running tox invokes various commands (such as building the
package, pip installing dependencies and so on), these were
printed in case they failed as Python arrays. Changed the
representation to a shell command, allowing the users to quickly
replicate/debug the failure on their own - by
:user:`gaborbernat` (`#851
`_)
+ skip missing interpreters value from the config file can now be
overridden via the "--skip-missing-interpreters" cli flag - by
:user:`gaborbernat` (`#903
`_)
+ keep additional environments config order when listing them - by
:user:`gaborbernat` (`#921
`_)
+ allow injecting config value inside the ini file dependent of
the fact that we're connected to an interactive shell or not -
by :user:`gaborbernat` (`#947
`_)
+ do not build sdist if skip install is specified for the envs to
be run - by :user:`gaborbernat` (`#974
`_)
+ when verbosity level increases above two start passing through
verbosity flags to pip - by :user:`gaborbernat` (`#982
`_)
+ when discovering the interpreter to use check if the tox host
Python matches and use that if so - by :user:`gaborbernat`
(`#994 `_)
+ "-vv" will print out why a virtual environment is re-created
whenever this operation is triggered - by :user:`gaborbernat`
(`#1004 `_)
* Documentation
+ clarify that "python" and "pip" refer to the virtual
environments executable - by :user:`gaborbernat` (`#305
`_)
+ add Sphinx and mkdocs example of generating documentation via
tox - by :user:`gaborbernat` (`#374
`_)
+ specify that "setup.cfg" tox configuration needs to be inside
the "tox:tox" namespace - by :user:`gaborbernat` (`#545
`_)


Tomáš Chvátal's avatar

scarabeus_iv accepted request

openSUSE Build Service is sponsored by