I have created a script that enables conversion of nose.tools.assert_
function calls to raw assert statements. The project is at
https://github.com/schollii/nose2pytest. Where would be a good place to
post this so pytest users know about it? Thanks,
--
Oliver
Open Source contributions: PyPubSub
Thx Florian for the tips. I have finally gotten around to releasing on pypi
so I'll post to those places you suggested. Cheers,
Oliver
On Mar 20, 2016 7:52 AM, "Florian Bruhin" wrote:
> * oliver [2016-03-19 22:26:11 -0400]:
> > I have created a script th
functionality so I'm really curious to see if nose2test can be useful
to others.
I'm sure there is lots of room for improvement. Any feedback or
contributions would be much appreciated.
Regards,
Oliver
___
pytest-dev mailing list
pytest-dev@
On Fri, Apr 1, 2016 at 2:42 AM, Thomas De Schampheleire <
patrickdeping...@gmail.com> wrote:
> Hi Oliver,
>
> On Fri, Apr 1, 2016 at 6:17 AM, oliver
> wrote:
> > Thomas, is your idea that given test code like this:
> >
> > from unittest.case import Test
ted to
raw assertions can still be used without needing nose to be installed on
the system.
Oliver
Open Source contributions: PyPubSub <http://pubsub.sf.net/>, nose2pytest
<https://github.com/schollii/nose2pytest>, Lua-iCxx
<http://lua-icxx.sf.net/>, iof <http://i
> pytest-dev mailing list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
--
Oliver
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
On Tue, Oct 11, 2016, 18:57 Bruno Oliveira wrote:
> On Tue, Oct 11, 2016 at 7:46 PM oliver
> wrote:
>
> Is there any plan to port boxed and xdist plugins to Windows? What are the
> issues that have prevented implementation from happening (or happening
> sooner, if planned)?
iling list
> pytest-dev@python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
>
--
Oliver
My StackOverflow contributions
My CodeProject articles
My Github projects
My SourceForget.net projects
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
ard-declared one, keeps the interpreter happy. So it does the
job but because it is non-standard, IDE's don't know how to make use of
this information, and it is a bit annoying to have to write.
Is there really no way that this will *ever* be fixed so we don't need to
use string
Ah darned it yes! Thx for letting me know.
On Sun, Mar 5, 2017, 12:54 AM Florian Bruhin wrote:
> * oliver [2017-03-04 17:18:10 +]:
> > Is there really no way that this will *ever* be fixed so we don't need to
> > use strings or forward declaration hack?
>
> Did
Thank you for the update. It's nice to see people deal with conflict and
challenging behavior in a constructive and civilized manner, and to remind
people of what matters, the way you did. Keep up the awesome work. Cheers,
Oliver
On Wed., May 6, 2020, 3:43 a.m. Brianna Laugher,
wrote:
>
Makes sense to me.
On Thu, Dec 8, 2022 at 11:42 AM Floris Bruynooghe wrote:
> I'd also be +1 on this.
>
> Note however that the user in question did have 2FA enabled already and
> indeed this doesn't help for compromised tokens. I think we can force
> some limits on what tokens are allowed, I'm
ers of the source code that this is inline test code that is
not run when not reached via pytest. Eg I recommend `itest`, short, easy to
write, explicit.
Cheers,
Oliver
On Thu., Dec. 29, 2022, 4:39 a.m. Bruno Oliveira,
wrote:
> Hi Yuki,
>
> Sorry for the late reply, I think this notificat
On Fri., Dec. 30, 2022, 9:53 a.m. Yu Liu (Yuki),
wrote:
> Hi Bruno, Oliver, Floris,
>
> Thank you for the feedback! We have updated the README in our repo. We
> will also update the API from Here to itest, which may take some more
> time
>
Thank you Yu Liu and congratulati
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 re
appreciate the whole
pytest/tox/devpi toolchain and the ideas behind it, so I'll have go at
making myself useful while having some fun and learning from the jedi
masters of testing :)
cheers
Oliver
On Sat, 20 Feb 2016 at 15:30 Floris Bruynooghe wrote:
> Hi Oliver,
>
> On 17 February
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
Hi Raphael,
Abstract (longer version) -> is actually the short version and vice versa
cheers
Oliver
On Sun, 12 Jun 2016 at 23:00 Raphael Pierzina wrote:
> Hi,
>
> here’s my draft - I’d appreciate any last minute feedback! :)
>
> https://gist.gi
and if there is still some discussion
necessary regarding concrete topics an issue can be opened for that
concrete topic.
cheers
Oliver
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
+1 :)
On Wed, 6 Jul 2016 at 13:09 Bruno Oliveira wrote:
> Hi all,
>
> I have configured http://pytest.readthedocs.io/ to point to “latest” by
> default (which represents master branch) rather than “stable” (which
> represents “latest release/tag”). I think it makes more sense because
> usually o
uick hint? Oterrwise I'll just do the
PR against features branch in the unrestructured docs first.
Cheers
Oliver
On Sat, 9 Jul 2016 at 11:25 Florian Schulze
wrote:
> During one of the discussions I agreed to work on a small bit. Problem
> is, I didn't make a note and can&#
er to shut
the warnings up right in there as well (add hint about
``--disable-pytest-warnings``)?
Here's the gist:
https://gist.github.com/obestwalter/60080d472dc5c0a97ddc265e985f1aae
Cheers
Oliver
___
pytest-dev mailing list
pytest-dev@python
Hi Bruno and Daniel,
thanks for reviewing.
@Bruno will add the silence option also then like suggested
@Daniel: yeah I actually stumbled over that sentence while reading through
it again a bit later. Really not necessary. Even shorter - nice :)
Cheers
Oliver
On Mon, 11 Jul 2016 at 22:58
Hi,
I will prepare a PR with the little text about deprecation at the weekend.
Although I would also love to help with the rest of the docs restructuring,
I am not sure if I can carve out some time for this.
Cheers
Oliver
On Fri, 15 Jul 2016 at 01:14 Bruno Oliveira wrote:
> On Thu, Jul
explaining the policy).
I created it against the features branch as I am not sure if the
documentation restructuring will make it into 3.0
Cheers
Oliver
On Fri, 15 Jul 2016 at 18:06 Florian Bruhin wrote:
> * Floris Bruynooghe [2016-07-15 15:29:18 +0100]:
> > On 14 July 2016 at 23:45, Briann
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
O
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 wrote:
> Hi Bruno,
>
> wow, you'r
get around to do that, as I have some other topics I
have to see to first.
Cheers
Oliver
On Sun, 18 Sep 2016 at 13:05 Ronny Pfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:
> Hi Oliver,
>
> your pull request that was directly in the branch is already converted to
> a bran
on Bitbucket now links to an unrelated issue
on Github. Is that expected fallout from the move or would you have
expected this to do the right thing on Github now?
Cheers
Oliver
On Sat, 17 Sep 2016 at 22:14 Ronny Pfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:
> Hello everyone,
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
he project (section 2.3).
Giving everybody commit rights who successfully merged a PR is a different
idea that could be experimented with, but I would not call it C4.
Cheers
Oliver
On Tue, 15 Nov 2016 at 21:18 Floris Bruynooghe wrote:
> Cool, I'll create a PR against CONTRIBUTING.tx
Hi Floris,
thanks for the clarification.
Cheers
Oliver
On Wed, 16 Nov 2016 at 20:42 Floris Bruynooghe wrote:
> On 15 November 2016 at 23:19, Oliver Bestwalter
> wrote:
> > Hi,
> >
> > will this be a "sorta kinda C4" then or do we want to implement the who
- or is this pytest specific?
Cheers
Oliver
On Tue, 24 Jan 2017 at 21:34 Bruno Oliveira wrote:
> On Sat, Jan 21, 2017 at 1:10 AM Ana Ribeiro
> wrote:
>
> Hello,
>
> About what would we gain from that, Google gives U$D 5,500 for every
> student who completes the progra
a mentor myself to learn to
better tackle these things ;)
Cheers
Oliver
On Wed, 25 Jan 2017 at 12:31 Ana Ribeiro
wrote:
> Hello,
>
> Sorry, when I read the email too quickly and I thought of the browser
> (Tor) instead of Tox (shame)... For sure, I have used Tox on my internship.
&
want to work explicitly on tox and someone wants to mentor I
would suggest:
Generalize package builds and virtualenv creation:
https://github.com/tox-dev/tox/issues/338
as an interesting topic to tackle.
Cheers
Oliver
On Wed, 8 Feb 2017 at 15:49 Bruno Oliveira wrote:
> On Wed, Feb 8, 2017 at 1
Hey Oliviera!
done :D
On Fri, 10 Feb 2017 at 15:45 Bruno Oliveira wrote:
> Hi Walter, :)
>
> On Fri, Feb 10, 2017 at 11:52 AM Oliver Bestwalter
> wrote:
>
> If students want to work explicitly on tox and someone wants to mentor I
> would suggest:
>
> Generalize pa
On Fri, 10 Feb 2017 at 16:21 Oliver Bestwalter wrote:
Hey Oliviera!
[Note the subtle reordering of the letters to mark the way I pronounce this
in my head] - I'll see myself out now.
___
pytest-dev mailing list
pytest-dev@python.org
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
Hello Ronny,
oh wow! congratulations then :)
Cheers
Oliver
On Fri, 17 Mar 2017 at 10:16 Ronny Pfannschmidt <
opensou...@ronnypfannschmidt.de> wrote:
> Hi all,
>
> i'd love to join a sprint in some way, but i do have a kid on the way and
> its due end of july.
>
,
Cheers
Oliver
On Fri, 17 Mar 2017 at 11:49 Bruno Oliveira wrote:
> Hi,
>
> While this kind of change is a little disruptive regarding history and
> might generate conflicts in PRs, it is the kind of change that is a little
> pain for a short time but brings tangible benefits in th
eople that would want to do that, we could have a
tox/pytest/devpi helpdesk :)
Cheers,
Oliver
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
weekend.
Cheers
Oliver
On Tue, 28 Mar 2017 at 10:22 Dave Hunt wrote:
> I’m thinking of coming to EuroPython, and would be happy to spend some
> time at the helpdesk. My particular area of expertise would be the plugins
> I maintain, but I’m sure I can also answer some pytest/tox/devpi quer
Hi,
I wrote a mail to ask. I also noticed that the call for proposals is closed
already, I asked anyway - maybe there is still some room for us.
Cheers
Oliver
On Mon, 3 Apr 2017 at 16:51 Ionel Cristian Mărieș
wrote:
> I'm interested in this as well (pytest-cov/benchmark and genera
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 wrote:
> Hi,
>
> I wrote a mail to ask. I also noticed that the call for proposals is
> closed
etrize(
"req, exp", (
('foo', True),
('bar', False),
('BLARF', ValueError),
('PLONK', IndexError),
))
def test_something(arg, exp):
with pytest.raises_or_returns_or_yields_or_whatever(exp):
something(arg)
**shudder**
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 wrote:
> 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 ...
>
&g
Hi Dave,
no problem - was looking forward to see you to though. Are you attending
Pycon US? I might be there for the sprints.
Cheers,
Oliver
On Mon, 24 Apr 2017 at 15:56 Dave Hunt wrote:
> Unfortunately I’ve decided not to attend EuroPython this year, so I’ll
> need to revoke my offer t
Hi all,
I just got a mail that the helpdesk proposal was accepted. The date is not
scheduled yet. Will keep you posted.
Cheers,
Oliver
On Mon, 24 Apr 2017 at 17:03 Dave Hunt wrote:
> Unfortunately not. Might be able to attend a pytest sprint if one is
> planned, but otherwise it’ll pr
ols that I can use in my daily life instead of
being stuck with prorietary cr***. It's not like somebody dies because my
testing framework broke my CI builds, so I always try to keep things in
perspective :)
Cheers,
Oliver
On Sun, 21 May 2017 at 13:28 Floris Bruynooghe wrote:
> Ron
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 wrote
projects I threw it at (tox and
some private and work projects).
Cheers,
Oliver
On Fri, 14 Jul 2017 at 14:06 Bruno Oliveira wrote:
> Hi Florian,
>
> I definitely agree with you about making it clear what users have to do to
> replace deprecated functionality, which brings to attention t
Hi Daniele,
sounds great! I might join you later to figure out if this might also be a
good idea for tox. What about changed urls though? Is there some strategy
to keep old links intact or do proper redirects?
Cheers,
Oliver
On Sat, 15 Jul 2017 at 12:32, Daniele Procida wrote:
> Dear pyt
ge
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 <
opensou...@ronnypfannschmidt.de> wrote:
> Hi everyone,
>
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,
>
&
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
k that this the definite way forward. Or ... if that
won't happen just having a shared account sharing the secrets through
keybase.io
Cheers,
Oliver
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
Thank you Ringo,
I have no immediate plans to implement something like this but I would
definitely appreciate some further docs/explanations/blog that unravels how
it is accomplished.
Cheers,
Oliver
On Fri 20. Apr 2018 at 08:26, Ringo De Smet
wrote:
> Floris, Oliver,
>
> If you want,
any of you are also there and would like to hang out with me and help
some folks to get their questions answered, I would be happy.
I will let you know if the proposal was accepted.
Cheers,
Oliver
___
pytest-dev mailing list
pytest-dev@python.org
https
Hi Dave,
great! Looking forward to hang out with you :)
Cheers,
Oliver
On Mon, 21 May 2018 at 15:31 Dave Hunt wrote:
> Hey Oliver,
>
> I’m there Monday-Saturday and would be happy to help out where I can!
>
> Cheers,
> Dave
>
> > On 20 May 2018, at 15:47,
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
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
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:
>
> https://www.packtpub.com/web-deve
rrors inheriting from that
ReportableError or KnownError could then be caught at the top level and be
reported differently without a noisy traceback (e.g. only printing out the
place where it occured and the error type and message).
Cheers,
Oliver
On Thu, 4 Oct 2018 at 15:51 Florian Bruhin
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 except
n more frequent releases that contain smaller changesets and also to not
shy away from more frequent major releases, if that makes the transition
easier.
Thanks that you care and thanks for all your work
Oliver
On Wed, 7 Nov 2018 at 20:56 Bruno Oliveira wrote:
> Hi Ronny,
>
> On Wed, Nov
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
par
I'm happy to help out with pytest and
> friends!
ok, sounds good :)
Cheers,
Oliver
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
69 matches
Mail list logo
