eriknw / toolz

100%

master: 100%

LAST BUILD ON BRANCH faster_remove

branch: faster_remove

CHANGE BRANCH

x

Reset

• faster_remove
• authors_larsmans_josericardo
• authors_shvechikov
• backport_tests
• better_curry_error
• better_curry_introspection
• clean_curried_namespace
• consume
• correct_flip_doctest
• coveralls
• coveralls_for_master
• coveralls_success_only
• curry_class
• curry_classmethods
• curry_makeover
• curry_memoize
• curry_numargs
• curry_reduce
• dict_iter
• diff
• equality_hash_key
• explicit_curried
• faster_groupby
• faster_merge_sorted
• faster_merge_with
• faster_unique
• fix/curry_module
• fix/ensure_easy_testing
• fix_32bit_overflow
• fix_property_introspection
• get_with_itemgetter
• identical
• isdistinct_for_iterators
• itemmap
• jackknife_sandbox
• juxt_generator
• juxt_tuple
• last_with_deque
• memoize_key_func
• memoize_unary
• more_introspection
• nth_with_list
• pep479
• pypy3
• python3.6
• readme_broken_links
• readme_rst
• remove_jackknife
• run_doctests_on_curried
• serialize_juxt
• svg_badges
• test_curry_too
• test_dicttoolz_types
• tlz
• unused_variables
• update/pluck_docstring

Build # 85

Build Type

push

travis-ci

Committed by eriknw

Commit Message

Faster `remove` by using `filterfalse`, which was added to `compatibility`

Also, a typo (it lied!) was fixed in the documentation of `remove`

By using `filterfalse`, we modify the behavior of `remove` when `None` is
used as the predicate.  Previously, `remove(None, [0, 1, 2])` raised
`TypeError`.  Now it returns `[0]`.  If we want the former, we can add a
check for `None`.

Run Details

455 of 455 relevant lines covered (100.0%)

4.0 hits per line