Hi Florian,
I have this problem as well and was trying to find a better solution before
bringing up this issue, but let me share my solution so far.
The problem is that the mechanism for plugin discovered used by pytest
(setupttools entry points) doesn't work with frozen executables so pytest
Hey,
* Bruno Oliveira nicodde...@gmail.com [2015-06-18 13:50:59 +]:
The problem is that the mechanism for plugin discovered used by pytest
(setupttools entry points) doesn't work with frozen executables so pytest
can't find any plugins.
Hm, I see. I'm not really aware how setuptools entry
Nice, thanks for sharing! :)
Cheers,
On Thu, Jun 18, 2015 at 12:21 PM Florian Bruhin m...@the-compiler.org wrote:
Another solution would be to explicitly pass the plugin in the command
line
using `-p pytestq.plugin`.
Sorry for the double-post - I found an (IMHO) slightly better solution
On Thu, Jun 18, 2015 at 2:47 AM holger krekel hol...@merlinux.eu wrote:
On Wed, Jun 17, 2015 at 22:06 -0700, Floris Bruynooghe wrote:
I think Ronny had some 2.7.2 plans as well or wanted it soon for some
reason?
pytest-cache integration into the core perhaps?
Maybe we can just aim for
On Thu, Jun 18, 2015 at 6:49 PM Laura Creighton l...@openend.se wrote:
So I think this is a great idea. I see no downside at all.
What would it be?
People commented on the issue I posted supporting this idea, so I moved
this forward by requesting to add a new Trove classifier here:
On Thu, Jun 18, 2015 at 10:22 +0200, Tibor Arpas wrote:
How about the new hook call system vs the old __multicall__ ? Is the plan
still to deprecate the old way in 2.8 and remove in 2.9?
yes, that's the plan.
Any idea how many plugin-s use it and will brake (or were already updated)?
IIRC
