![](https://secure.gravatar.com/avatar/1816aaddac0110ea78185e7759156907.jpg?s=120&d=mm&r=g)
But tests taking 1.48 longer to run on average! Anything I should know about 3.6 and performance? On 18 November 2016 at 22:42, Luca Sbardella <luca.sbardella@gmail.com> wrote:
Pulsar's tests are now run against 3.6-dev and all passing. Nice! Getting used to the C Future ;-)
On 13 October 2016 at 06:37, INADA Naoki <songofacandy@gmail.com> wrote:
Thanks, Ben.
Both are very helpful information!
On Thu, Oct 13, 2016 at 2:25 PM, Ben Darnell <ben@bendarnell.com> wrote:
[+async-sig@python.org, which is the new home for these kinds of discussions]
Tornado's tests are now failing on nightly with "TypeError: can't send non-None value to a FutureIter": https://travis-ci.org/tornadoweb/tornado/jobs/167252979
-Ben
On Tue, Oct 11, 2016 at 3:55 PM INADA Naoki <songofacandy@gmail.com> wrote:
If you have asyncio based project, and it uses Travis-CI,
please add "nightly" to your .travis.cnf [2].
[2]
Python-versions-to-test-against
Travis changed the "nightly" version to 3.7
Now "3.6-dev" is for Python 3.6beta (Still 3.6b1, it may be upgraded soon).
--
INADA Naoki <songofacandy@gmail.com>
-- INADA Naoki <songofacandy@gmail.com>