yes, it makes sense to fix failing tests, they're real problems. You
don't need to create the issue and you can just do the PR.
This is the appropriate mailing list, but we work a lot through IRC
On Sat, Jan 2, 2016 at 1:44 AM, Sergey Matyunin
wrote:
> Dear Maciej,
>
> Thanks for the answer!
> D
Dear Maciej,
Thanks for the answer!
Does it make sense to fix failing tests? Or may be they were left as
is because they are irrelevant?
Do numpypy developers use these tests or some other tests?
Does any guidelines exist for numpypy developers? Do I need to create
an issue for each PR?
Is this
This is the actual state
On Fri, Jan 1, 2016 at 11:43 PM, Sergey Matyunin
wrote:
> Hello,
>
> I am curious about the status of unit tests of numpy for pypy. Where
> can I get actual information about it?
>
> I have installed pypy 4.0.1, numpypy for it (tag 4.0.1) and launched
> numpy tests using
Hello,
I am curious about the status of unit tests of numpy for pypy. Where
can I get actual information about it?
I have installed pypy 4.0.1, numpypy for it (tag 4.0.1) and launched
numpy tests using
numpy.test()
Looks like there is a plenty of failed tests:
> Ran 4157 tests in 15.592s
> FAILED
Hi Matti,
Happy new year :-)
On Fri, Jan 1, 2016 at 10:31 AM, Matti Picus wrote:
> Are the dates firm enough that I can order flights? It is getting late...
I should have the definitive confirmation tomorrow.
Armin
___
pypy-dev mailing list
pypy-dev
On 13/12/15 21:46, Armin Rigo wrote:
Hi all,
The sprint should be on the week of February, the 21-28th. A final
confirmation will have to wait for around two more weeks, but unless
there is really an unexpected problem, it should be this date. I will
of course sent a proper
