Hi,
thanks Florian - that sounds great. I would also appreciate that on the
first sprint day. I will be arriving on the 19th in the afternoon. I a
started working my way into the code base of pytest but I am also very
interested in working on tox.
Cheers
Oliver
On Wed, 1 Jun 2016 at 14:18
Hello,
I would like to participate in the sprint and I won't need any funding.
My name is Oliver Bestwalter and I live in Ravensburg near Lake Constance.
I fell in love with Python in 2006 and work at Avira since 2011. I am part
of a small team that is automating internal build, test and release
On 17 February 2016 at 11:08, Oliver Bestwalter <oli...@bestwalter.de>
> wrote:
> > I would like to participate in the sprint and I won't need any funding.
>
> Great that you want to join us!
>
> > I am using py.test in all my pet projects and professionally since 2011
Hi all,
I just opened a PR adding the docs about our backwards compatibility
policy: https://github.com/pytest-dev/pytest/pull/1736
With that PR all necessary elements are in place as discussed (internal
pytest warnings on by default, possibility to silence these warnings,
documentation
Hi all,
I created a wiki page containing the checklist for the 3.0 release that
resulted from our discussion during the sprint.
https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist
I think that is better than opening an issue, because everybody involved
can update the page directly
Hello,
o.k. sounds all good to me then.
I have a topic in mind already that could nicely be tackled which is what
we started to draft already as part of the sprint:
https://github.com/tox-dev/tox/blob/master/doc/drafts/extend-envs-and-packagebuilds.md
- if we find a dedicated individual who
Hi all,
I had a closer look at the timeline and what is involved and I think I
would overreach myself if I would volunteer as a mentor this year already.
I am basically a newbie to tox myself, so I better buckle down a bit first.
I guess I will feel up to the task next year then.
If students
Hi Bruno,
wow, you're fast! Great! I wanted to do some testing over the weekend with
the release candidate. Will do it with 3.0 now instead :)
What I can already say is that I checked the feature branch against my main
projects since the sprint and didn't have any problems.
Cheers
Oliver
On
I updated the checklist to reflect the current status as that is the first
hit, if somebody is searchin for pytest 3.0 atm.
https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist
Cheers
Oliver
On Sat, 20 Aug 2016 at 11:20 Oliver Bestwalter <oli...@bestwalter.de> wrote:
> Hi Bruno,
>
>
Hello Ronny,
thanks a lot for going through the major PITA of doing such a move!
One thing I noticed is that the 4 remaining pull requests have not been
migrated. How can we deal with them?
Also see: https://github.com/tox-dev/tox/issues/352#issuecomment-247791365
The link to the pull request
Hi Florian,
I really appreciate, that you opted for the harder but better quality
route. The quality is really good - this comes from an enthusiastic T-Shirt
wearer since the early 1980s - so thanks for going through all the trouble
:)
Cheers
Oliver
On Tue, 25 Oct 2016 at 15:43 Florian Bruhin
Hi Floris,
thanks for the clarification.
Cheers
Oliver
On Wed, 16 Nov 2016 at 20:42 Floris Bruynooghe <f...@devork.be> wrote:
> On 15 November 2016 at 23:19, Oliver Bestwalter <oli...@bestwalter.de>
> wrote:
> > Hi,
> >
> > will this be a "sorta
Hi,
will this be a "sorta kinda C4" then or do we want to implement the whole
thing as described in https://rfc.zeromq.org/spec:42/C4/ ?
I ask because what you describe Floris is an interesting idea but I do not
see the parallel to C4 as that process clearly has maintainers who merge
PRs of
Hi all,
EuroPython is on the horizon and they have a new thing (or at least new for
me) called "helpdesk"
> Helpdesk / 10 slots
> Helpdesks are a great way to share your experience on a technology, by
offering to help people answering their questions and solving their
practical problems. You
Hi all,
just want to get the ball rolling and ask if planning has started already
and how I can help.
This is mainly triggered by a question here:
https://github.com/tox-dev/tox/issues/485
Would it maybe be feasible to coordinate this together with the EuroPython
this year?
Cheers,
Oliver
h is also why i can't participate in planning this year and also
> likely can't be there in person.
>
> -- Ronny
>
> On 15.03.2017 13:47, Oliver Bestwalter wrote:
>
> Hi all,
>
> just want to get the ball rolling and ask if planning has started already
> and how I can he
Hi all,
I usually have all flake8 on full throttle and let PyCharm warn me (except
for naming, I am a bit particular there I admit) and I have similar
thoughts when wondering through the tox sources. I will watch how you do it
and then maybe propose the same for tox afterwards.
Good luck,
http://blog.ionelmc.ro
>
> On Mon, Apr 3, 2017 at 5:25 PM, Oliver Bestwalter <oli...@bestwalter.de>
> wrote:
>
> Hi all,
>
> I just got the green light to go to EuroPython, so I volunteer to do the
> proposal and in the worst case I will be helpdesking away on my own, but I
Hi,
I don't know what I saw yesterday, but the call for proposals ist not
closed, There is time untill the 16th of April ...
Oliver
On Mon, 3 Apr 2017 at 22:57 Oliver Bestwalter <oli...@bestwalter.de> wrote:
> Hi,
>
> I wrote a mail to ask. I also noticed that the cal
Hi,
I am reading this thread with growing fascination, because I have the
feeling I am missing something, so can I summarize?
If I had a test, where I don't care about output and only about whther
exceptions are thrown or not I would normally write this:
@pytest.mark.parametrize(
"req,
Hi,
+1 for making releases easier.
Just a thought on the side: mid to long term we might even be able to
synchronize workflows between projects and do something like jazzband (
https://jazzband.co/) for pytest/tox/devpi and plugins that are maintained
by the community.
Cheers,
Oliver
On Wed,
ou
turn up :)
I'll keep you posted if the proposal was accepted.
Cheers,
Oliver
On Tue, 4 Apr 2017 at 16:16 Oliver Bestwalter <oli...@bestwalter.de> wrote:
> Hi,
>
> I don't know what I saw yesterday, but the call for proposals ist not
> closed, There is time untill the
Hi Bruno,
I tried to install it into an existing Python 3.6 virtualenv and it
stumbled over setuptools - running it again in the same env worked then. I
pasted the call and a pip freeze here in case it is of interest:
https://pastebin.com/xW7KfuuN
Besides from that it works fine with the
Hi all,
the date for the helpdesk is tuesday from 10:30 to 12:00 and again from
14:00 to 15:30.
I am also there on sunday and will stay for the sprints and do some work on
tox, if you are interested to join in.
See you in Rimini
Oliver
On Fri, 12 May 2017 at 21:33 Oliver Bestwalter <
> I maintain, but I’m sure I can also answer some pytest/tox/devpi queries
> too.
>
> Cheers,
> Dave
>
> On 27 Mar 2017, at 21:42, Oliver Bestwalter <oli...@bestwalter.de> wrote:
>
> Hi all,
>
> EuroPython is on the horizon and they have a new thin
Hi all,
this is a bit meta, as I have not enough insight about the topic at hand (I
did not follow the discussion closely), but as the one who proposed the
policy at the last sprint, I feel obliged to give my two cents about that
aspect of the discussion. I also try to give my perspective as a
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
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 <oli...@bestwalter.de> wrote:
Hi,
and I just saw that pytest added coverage long ago - should have known :)
Cheers,
Oliver
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
Hi,
I will be attending the EuroPython and just submitted the same proposal
like last year to run a pytest/tox/devpi helpdesk. Last year was fun and
most people who came had not much experience with the tools yet and were
looking for some help introducing automated testing in their projects.
If
Hi Dave,
great! Looking forward to hang out with you :)
Cheers,
Oliver
On Mon, 21 May 2018 at 15:31 Dave Hunt <dh...@mozilla.com> wrote:
> Hey Oliver,
>
> I’m there Monday-Saturday and would be happy to help out where I can!
>
> Cheers,
> Dave
>
> > On 20 May
Hello all,
I just got confirmation that the help desk proposal was accepted. See you
in Scotland then :)
Cheers,
Oliver
On Mon, 21 May 2018 at 15:52 Oliver Bestwalter wrote:
> Hi Dave,
>
> great! Looking forward to hang out with you :)
>
> Cheers,
> Oliver
>
> On M
Hi,
I was following along and will propose the same for tox where I will also
volunteer as a contact, so might as well volunteer here.
Would be great though if there also was a female person available for
contact (if possible then also for tox, if we do thr same there).
Cheers,
Oliver
On Sat 4.
H Bruno,
congratulations! Bought it right away - coming from you it has to be good :)
Cheers,
Oliver
On Thu, 30 Aug 2018 at 17:09 Bruno Oliveira wrote:
> Hi everyone,
>
> I'm pleased to announce the release of my book about pytest:
>
>
sounds good.
On Fri 6. Jul 2018 at 20:43, Floris Bruynooghe wrote:
> On Fri 06 Jul 2018 at 12:13 -0300, Bruno Oliveira wrote:
> > GitHub has started issue warnings that the email service we use to notify
> > pushes to master and features will be discontinued (and we suspect it is
> > not working
t; Floris, Oliver,
>
> If you want, I can get you bootstrapped on this Terraform setup. I can say
> I almost know Terraform inside out. ;-)
>
> Ringo
>
> On Thu, Apr 19, 2018 at 9:17 PM, Oliver Bestwalter <oli...@bestwalter.de>
> wrote:
>
>> Hi,
>>
>> Flor
Hi,
Floris wrote:
> That's a nice bit of automation.
I like the idea that it works somehow, but after looking at the README it
is still undistinguishable from magic to me.
Floris wrote:
> [0] Bonus points for whoever contributes a teams functionality to
warehouse!
This is why I think that this
Hi Ronny,
I'd like to add my 2 cents from the perspective of an enthusiastic pytest
user, who dabbles in a lot of projects using pytest and who occasionally
teaches it:
I use pytest since 2010 and can still remember a time when I was able to
trigger the dreaded quite regularly and it was often
Glad to help Oliveira ;)
On Thu, 4 Oct 2018 at 21:28 Bruno Oliveira wrote:
> Hi Walter ;)
>
> On Thu, Oct 4, 2018 at 4:21 PM Oliver Bestwalter
> wrote:
>
>> About the naming things problem: I don't know if this is overkill, but
>> how about having an exceptio
Hi,
I think this is a great idea.
About the naming things problem: I don't know if this is overkill, but how
about having an exception like e.g. ReportableError or KnownError that
errors like using an invalid scope in your example can inherit from (e.g.
InvalidScope) can inherit from. All errors
Hey,
On 4/24/19 9:44 PM, Florian Bruhin wrote:>
> Any other pytest-related plans? Oliver, do you plan to host another
helpdesk
> like in 2017/2018?
Yes, I will propose doing a pytest/tox/devpi helpdesk again.
I would also love to assist you with your training (like helping
participants
Hi Florian,
On Thu, 25 Apr 2019 at 11:22, Florian Bruhin wrote:
> Yay! Feel free to add me there as well if you want:
Great. Will do.
> I'll definitely need some helpers again, thanks for the offer! Apparently the
> training rooms have a capacity of 100 seats, and at least 2015/2016 there were
42 matches
Mail list logo
