On 23 March 2017 at 20:41, Ned Batchelder wrote:
>>> If unittests searches normal directly, it may walk deep into very
>>> large tree containing
>>> millions of directories. I don't like it.
>
>> That is a risk, OTOH I think the failure to do what folk expect is a
>> bigger risk.
>
> The issue he
On 3/23/17 3:14 PM, Robert Collins wrote:
> On 24 March 2017 at 04:59, INADA Naoki wrote:
>> And this issue is relating to it too: http://bugs.python.org/issue29716
>>
>> In short, "namespace package" is for make it possible to `pip install
>> foo_bar foo_baz`,
>> when foo_bar provides `foo.bar` a
On 24 March 2017 at 04:59, INADA Naoki wrote:
> And this issue is relating to it too: http://bugs.python.org/issue29716
>
> In short, "namespace package" is for make it possible to `pip install
> foo_bar foo_baz`,
> when foo_bar provides `foo.bar` and foo_baz provides `foo.baz`
> package. (foo is
And this issue is relating to it too: http://bugs.python.org/issue29716
In short, "namespace package" is for make it possible to `pip install
foo_bar foo_baz`,
when foo_bar provides `foo.bar` and foo_baz provides `foo.baz`
package. (foo is namespace package).
If unittests searches normal directl
There is already http://bugs.python.org/issue29642
On Thu, Mar 23, 2017 at 11:04 PM, Ilya Kazakevich
wrote:
> Hello.
> I have following layout:
>
> \---tests
> | test_module.py
> | __init__.py
>
>
> When I launch "python.exe" -m unittest discover -t . -s tests" it works
> perfectly.
>
