Mailman 3 - tox-dev - python.org

Pushed an unnecessary merge commit
by Oliver Bestwalter 27 Mar '17

27 Mar '17

Hi all, I just wanted to let you know that I pushed an unnecessary merge to master ( https://github.com/tox-dev/tox/commit/26354873eeb7062481342fa819aa583de2b0c…). I still need to learn how to be a contributor who opens PRs to be reviewed and a maintainer who does things directly on master at the same time. I hope my push license won't be revoked because of this, but I take this as a chance to ask for some feedback. I don't know how the more experienced devs handle this, but this is my current approach: if I see something that needs to be done that carries no risk and is uncontroversial I just do it without bothering anyone. It's all in the git history anyway. If I feel in any way insecure about the change, I go the normal route (PR or Issue or writing on the mailing list). Here are some things that fall into that first group for me: * Fixing typos, fix broken links, improve grammar in docs * Completing merged PRs like adding missing changelog entries or fixing minor oversights * changing long_description of the project, so the changelog entries of the last 5 releases are shown on pypi (suggestion from Florian to do the same as in devpi) * fixed some problems due to a merged PR that turned out to be slightly incomplete and lacked some test coverage (although there was something I did not feel sure about which I reverted then). * Preparing releases (bumping version numbers, etc.) * etc. https://github.com/tox-dev/tox/commits?author=obestwalter ... so in short a lot of stuff that is not very exciting to do, but from my current understanding part of the work of a maintainer. Those things are utterly boring if somebody else is asked to look over it and it makes no sense from my point of view to waste other peoples time with that. This also includes things where it is more work and delay to remind somebody else to do it instead of just fixing it yourself. Here are some things I opened a PR or Issue for: * Adding a Vagrantfile * Changing the way versioning is handled (introducing setuptools_scm) * Replacing all references to an old domain, where I was not quite sure if it is really obsolete * etc. https://github.com/tox-dev/tox/issues/created_by/obestwalter So that's where I stand now and that is how I am planning to carry on, unless I get new information that would lead me to reconsider that approach. Cheers, Oliver

4 4

tox 2.7 is looming
by Oliver Bestwalter 25 Mar '17

25 Mar '17

Hi all, the merged PRs start piling up, and we have a few new features but no backwards incompatibilities I would know of, so I bumped the minor version and pushed a dev version to my index: https://devpi.net/obestwalter/dev/tox/2.7.0.dev1 The pace of development and the complexity of the fixes do not justify to shower you with reams of text, so just have a look at the CHANGELOG and the referenced issues for details. I will be using that version over the next week for my projects at work and release it next friday if everything stays quiet here. The not yet merged PRs I would like to carry over into the next release as some feedback would still be appreciated about the changing of the default hook behaviours in https://github.com/tox-dev/tox/pull/450 and the setuptools_scm switch is nothing really urgent, so that does not have to go with 2.7 either. Cheers, Oliver

1 0

Introducing projects
by Oliver Bestwalter 10 Mar '17

10 Mar '17

Hi all, I started using projects for the tox issues: https://github.com/tox-dev/tox/projects Github projects are simple boards to provide additional views on the issues and organize the flow of issues. It basically turns issues into virtual post its, which then can be priritized and move along the different stages of realization, it has very little overhead and I like that way of getting organized. the first "official" project is to prioritize the open bugs by severity to be grabbed from the top for motivated bug squashers :) - see https://github.com/tox-dev/tox/projects/1 I don't know if it is a good idea for a project like tox, but I will start using this to get my own maintenance/OSS gardening work organized and maybe it is interesting or helpful for other contributors as well. Cheers Oliver

3 5

Next releases tox/detox
by Oliver Bestwalter 10 Mar '17

10 Mar '17

Hi all, I would like to establish a regular-ish release flow for tox and detox. PRs are trickling in in a pleasant but not overwhelming number atm and I would think that minor releases could be done quite often. I will try to make releases as easy and foolproof as possible by adding a bit more automation there. Like I proposed somewhere else already, as a first step I will add Ronnies setuptools_scm to handle versioning and a Vagrantfile that will make local testing on Linux and Windows easier for contributors. Related issues are: https://github.com/tox-dev/tox/issues/455 and https://github.com/tox-dev/tox/issues/474 Cheers, Oliver

1 0

2.6.0 release tomorrow
by Oliver Bestwalter 03 Feb '17

03 Feb '17

Hi all, after some teething problems I am now all set up to do releases and will do the first one tomorrow. All tests are green on Linux and Windows. Will try to run tests also on a Mac I have lying around at work tomorrow and then push it to pypi. I would appreciate some extra eye balls, so if someone wants to look at the package, it is here: https://devpi.net/obestwalter/dev/tox/2.6.0 Cheers Oliver

5 23

tox-2.5.0: little fixes and improvements
by holger krekel 16 Nov '16

16 Nov '16

hi all, tox-2.5.0 was just released to pypi, see https://tox.readthedocs.org for docs and the changelog below for details. Many thanks to Oliver Bestwalter, Ronny Pfannschmidt, Bruno Oliveira, Lukasz Rogalski, John Vandenberg, Florian Bruhin and all others who submitted issues and helped resolve them. best, holger krekel 2.5.0 ---------- - slightly backward incompatible: fix issue310: the {posargs} substitution now properly preserves the tox command line positional arguments. Positional arguments with spaces are now properly handled. NOTE: if your tox invocation previously used extra quoting for positional arguments to work around issue310, you need to remove the quoting. Example: tox -- "'some string'" # has to now be written simply as tox -- "some string" thanks holger krekel. You can set ``minversion = 2.5.0`` in the ``[tox]`` section of ``tox.ini`` to make sure people using your tox.ini use the correct version. - fix #359: add COMSPEC to default passenv on windows. Thanks @anthrotype. - add support for py36 and py37 and add py36-dev and py37(nightly) to travis builds of tox. Thanks John Vandenberg. - fix #348: add py2 and py3 as default environments pointing to "python2" and "python3" basepython executables. Also fix #347 by updating the list of default envs in the tox basic example. Thanks Tobias McNulty. - make "-h" and "--help-ini" options work even if there is no tox.ini, thanks holger krekel. - add {:} substitution, which is replaced with os-specific path separator, thanks Lukasz Rogalski. - fix #305: ``downloadcache`` test env config is now ignored as pip-8 does caching by default. Thanks holger krekel. - output from install command in verbose (-vv) mode is now printed to console instead of being redirected to file, thanks Lukasz Rogalski - fix #399. Make sure {envtmpdir} is created if it doesn't exist at the start of a testenvironment run. Thanks Manuel Jacob. - fix #316: Lack of commands key in ini file is now treated as an error. Reported virtualenv status is 'nothing to do' instead of 'commands succeeded', with relevant error message displayed. Thanks Lukasz Rogalski.

1 0

Logo is in the works - how about a slogan?
by Oliver Bestwalter 07 Nov '16

07 Nov '16

Hi, in the logo discussion the term "Testing out of the box" came up as the thought behind the name. I think this is a great slogan for the project as well, so I am wondered why it is not used more prominently. When I google for it I come up with http://testoob.sourceforge.net/ which was last updated in 2009 on PyPI and looks pretty dead to me. On the other hand, tox is often used more like a makefile nowadays (do more stuff additionally to testing like building documentation, deployments whatever should be automated and easy to reach) ... at least by me :) - so as much as I like the slogan it might actually not cover completely what tox is. I also explain tox as a command line CI frontend sometimes, but that is obviously only making sense to people who know what CI is and what challenges it presents. I would be interested in your opinion about what tox is and how one could describe it in a few words and if you think that a slogan might be a nice thing to have. Cheers Oliver

1 0

logo for tox: wishes, ideas?
by holger krekel 07 Nov '16

07 Nov '16

Hey all, welcome to the new tox-dev mailing list :) Jad, on initiative of Florian Bruhin, has offered to create a logo for tox. He even did a few sketches, see attachment. I then gave him the following preliminarily input from my side: > tox: "testing out of the box" was one thing that led to the name. I > like > your (2), (3) and (4) designs best in that order. > > As to colors and shapes, it'd be cool if there were some aesthetic and > color relation to the https://pytest.org logo (meant to symbolize a > pan flute for herding goats and in python a (testing) goat is used > as in "obey the testing goat"). So here i'd like to ask for your thoughts, brainstorming style, on what you suggest for the tox logo. Any wild inspirations? I am not going to involve Jad here to avoid overwhelming him and will rather see to integrate wishes ... My plan is to talk to him end of the week and ask for new sketches. Besides, we are probably soon to release a tox-2.5. Oliver already did a lot of work going through issues and some PRs were created and merged lately. cheers, holger

4 3