Elias481 / PyInotify

84%

master: 85%

LAST BUILD ON BRANCH fix-issue-41-guarantee-event_names-order

branch: fix-issue-41-guarantee-event_names-order

CHANGE BRANCH

x

Reset

• fix-issue-41-guarantee-event_names-order
• check-OSx-compatibility
• fix-handling-disappearing-subdirs
• fix-missing-errno-for-library-calls
• fix-remove_watch+_BaseTree.event_gen
• identify-todos-ajust-constants
• master
• pending-fixes
• pending-fixes--mergeprep
• pending-fixes--with2.6test
• release
• stay-2.6-compatible
• travis_chaches_test
• try-to-stay_2.6_compatible
• use-os.walk-for-recursing+add-ignored_dirs
• use-os.walk-for-recursing+add-ignored_dirs--merge
• use-os.walk-for-recursing+add-ignored_dirs--with2.6test

Build # 120

Build Type

push

travis-ci-com

Committed by Elias481

Commit Message

account for https://github.com/dsoprea/PyInotify/issues/41 - but do not change interface

* still lists are returned and we have to slowly copy them as fast as possible by slicing
* IS_DIR is always the second one so we always have the event on first position and the flag on second
preferrable would be to utilize tuples that wouldn't need to be copied because of their immutability or frozensets which are faster for "'EVENT_NAME' in event_name" expressions in case the possible second one in list is searched for...

(also I personally would prefer to get a fixed length tuple or no nested tuple at all but a boolean is-dir indicator and a string for the eventname... but anyway I prefer to use mask value for performance reasons...)

Run Details

240 of 285 relevant lines covered (84.21%)

3.37 hits per line