From opensource at ronnypfannschmidt.de Wed Sep 6 06:20:02 2017 From: opensource at ronnypfannschmidt.de (RonnyPfannschmidt) Date: Wed, 6 Sep 2017 12:20:02 +0200 Subject: [pytest-dev] [rant] introduction of the new mark api will be deferred further - due to bad rotten spaghetti code Message-ID: Hi everyone, due pretty much damn bad code quality and complete lack of tests in a? manageable granularity i am unable to move many internals to a new api anytime soon (things just fall apart sprinkled all over the place) additionally with the current state of tests its feels pretty much impossible to show what i need in a granular manageable and comprehensible manner (all the tests in the domain that i need to tighten/correct are end2end test which means they have zero value now that i need to change things) my current main problem is, that i cannot demonstrate the correct interaction of mark evaluation with nodes in a code amount that could fit a my head this is pretty much the results of years of neglecting to write fine granular tests while also not cleaning up so the effort to fix this will require weeks of work and likely introduce accidental internal api breaks en mass as i try to get more granular tests working. I feel pretty much helpless? and betrayed in front of such a task, i'm not sure if i want to even start anymore. I'm pretty pissed off and angry that the code is at such a state to begin with. -- Ronny From oliver at bestwalter.de Wed Sep 6 12:29:19 2017 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Wed, 06 Sep 2017 16:29:19 +0000 Subject: [pytest-dev] [rant] introduction of the new mark api will be deferred further - due to bad rotten spaghetti code In-Reply-To: References: Message-ID: Hi all, maybe focussing all eforts on improving code and test quality for a while would be a good idea before attempting any big refactorings? Obviously you can't force anybody, but if that is a clearly stated intent of the pytest team combined with the warning that new features, etc. will be on the backburner for a while, might help? Also : How about organizing a dedicated code quality and test quality sprint next year? I would love to help and have the chance of getting into the pytest code base a bit more. And just because the timing seems right: I could also offer to add coverage to the project, as I just did that for tox and it would be relatively straight forward for me to also do that for pytest now: https://codecov.io/gh/tox-dev/tox Cheers, Oliver On Wed, 6 Sep 2017 at 12:20 RonnyPfannschmidt < opensource at ronnypfannschmidt.de> wrote: > Hi everyone, > > due pretty much damn bad code quality and complete lack of tests in a > manageable granularity > i am unable to move many internals to a new api anytime soon (things > just fall apart sprinkled all over the place) > > additionally with the current state of tests its feels pretty much > impossible to show what i need in a granular manageable and > comprehensible manner (all the tests in the domain that i need to > tighten/correct are end2end test which means they have zero value now > that i need to change things) > > my current main problem is, that i cannot demonstrate the correct > interaction of mark evaluation with nodes in a code amount that could > fit a my head > > this is pretty much the results of years of neglecting to write fine > granular tests while also not cleaning up > > so the effort to fix this will require weeks of work and likely > introduce accidental internal api breaks en mass as i try to get more > granular tests working. > > I feel pretty much helpless and betrayed in front of such a task, i'm > not sure if i want to even start anymore. > > I'm pretty pissed off and angry that the code is at such a state to > begin with. > > -- Ronny > > _______________________________________________ > pytest-dev mailing list > pytest-dev at python.org > https://mail.python.org/mailman/listinfo/pytest-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver at bestwalter.de Wed Sep 6 12:31:54 2017 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Wed, 06 Sep 2017 16:31:54 +0000 Subject: [pytest-dev] [rant] introduction of the new mark api will be deferred further - due to bad rotten spaghetti code In-Reply-To: References: Message-ID: sorry, brain fart: I did not mean refactorings ... I actually meant the opposite: first refactor the code and tests to make it more maintainable and malleable before attempting to large scale functionality changes. On Wed, 6 Sep 2017 at 18:29 Oliver Bestwalter wrote: > Hi all, > > maybe focussing all eforts on improving code and test quality for a while > would be a good idea before attempting any big refactorings? Obviously you > can't force anybody, but if that is a clearly stated intent of the pytest > team combined with the warning that new features, etc. will be on the > backburner for a while, might help? > > Also : How about organizing a dedicated code quality and test quality > sprint next year? I would love to help and have the chance of getting into > the pytest code base a bit more. > > And just because the timing seems right: I could also offer to add > coverage to the project, as I just did that for tox and it would be > relatively straight forward for me to also do that for pytest now: > https://codecov.io/gh/tox-dev/tox > > Cheers, > Oliver > > On Wed, 6 Sep 2017 at 12:20 RonnyPfannschmidt < > opensource at ronnypfannschmidt.de> wrote: > >> Hi everyone, >> >> due pretty much damn bad code quality and complete lack of tests in a >> manageable granularity >> i am unable to move many internals to a new api anytime soon (things >> just fall apart sprinkled all over the place) >> >> additionally with the current state of tests its feels pretty much >> impossible to show what i need in a granular manageable and >> comprehensible manner (all the tests in the domain that i need to >> tighten/correct are end2end test which means they have zero value now >> that i need to change things) >> >> my current main problem is, that i cannot demonstrate the correct >> interaction of mark evaluation with nodes in a code amount that could >> fit a my head >> >> this is pretty much the results of years of neglecting to write fine >> granular tests while also not cleaning up >> >> so the effort to fix this will require weeks of work and likely >> introduce accidental internal api breaks en mass as i try to get more >> granular tests working. >> >> I feel pretty much helpless and betrayed in front of such a task, i'm >> not sure if i want to even start anymore. >> >> I'm pretty pissed off and angry that the code is at such a state to >> begin with. >> >> -- Ronny >> >> _______________________________________________ >> pytest-dev mailing list >> pytest-dev at python.org >> https://mail.python.org/mailman/listinfo/pytest-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From oliver at bestwalter.de Wed Sep 6 14:58:01 2017 From: oliver at bestwalter.de (Oliver Bestwalter) Date: Wed, 06 Sep 2017 18:58:01 +0000 Subject: [pytest-dev] [rant] introduction of the new mark api will be deferred further - due to bad rotten spaghetti code In-Reply-To: References: Message-ID: Hi, and I just saw that pytest added coverage long ago - should have known :) Cheers, Oliver -------------- next part -------------- An HTML attachment was scrubbed... URL: From nicoddemus at gmail.com Thu Sep 7 12:56:18 2017 From: nicoddemus at gmail.com (Bruno Oliveira) Date: Thu, 07 Sep 2017 16:56:18 +0000 Subject: [pytest-dev] pytest 3.2.2 released Message-ID: Hi everyone, pytest 3.2.2 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at http://doc.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Andreas Pelme * Antonio Hidalgo * Bruno Oliveira * Felipe Dau * Fernando Macedo * Jes?s Espino * Joan Massich * Joe Talbott * Kirill Pinchuk * Ronny Pfannschmidt * Xuan Luong Happy testing, The pytest Development Team -------------- next part -------------- An HTML attachment was scrubbed... URL: From charles at voleon.com Mon Sep 25 16:14:15 2017 From: charles at voleon.com (Charles Weitzer) Date: Mon, 25 Sep 2017 20:14:15 +0000 Subject: [pytest-dev] Opportunity at Voleon for test guru Message-ID: <747E9237-C677-4456-A97B-95EE459E74D4@voleon.com> The Voleon Group (www.voleon.com) is a technology-driven firm employing cutting-edge statistical machine learning techniques to investment management. Voleon has an opportunity for an exceptionally talented devops engineer to work on our core development team. This is a very unique, high impact opportunity to research, architect, develop, and deploy extremely sophisticated systems software. We are a dedicated Agile/Scrum shop. At Voleon your opinion, intellectual creativity, curiosity, and drive to succeed will be welcomed by our team. Our perfect candidate is someone who: - Has significant experience as an applications programmer. - Loves automating software development. - Is able to teach software engineers to integrate testing into their development. - Has experience in a wide variety of software development roles. - Is able to architect, grow, and manage a test team. - Has built a test environment at least once from scratch. - Is comfortable and able to work effectively with senior machine learning scientists and software engineers. Charles Weitzer Senior Recruiter The Voleon Group charles at voleon.com Office: +1 510.704.9870 x 7012 Mobile: +1 510 558-9182 www.voleon.com Confidential: This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Any comments or statements made herein do not necessarily reflect those of The Voleon Group, Voleon Funds LP, Voleon Capital Management LP, and their subsidiaries or affiliates. Please note that this e-mail has been created with the knowledge that Internet e-mail is not a 100% secure communications medium. We advise that you understand and observe this lack of security when sending and/or receiving email communications between Voleon Funds LP, Voleon Capital Management LP, and any of their subsidiaries/affiliates and yourself. Privacy: Voleon Funds LP, Voleon Capital Management LP, and their subsidiaries and affiliates archive incoming and outgoing emails and accordingly, may, at their discretion, monitor and review the content of all e-mail communications. This email should not be deemed to be an advertisement or solicitation. If so, or if you have received this e-mail on an unsolicited basis, and you believe you have received this message in error and/or do not wish to receive further e-mails, please contact unsubscribe at voleon.com referencing the sender's name and subject of the e-mail you are responding to. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: