pyinotify.Notifier.check_events() has lost all of its parameters

Bug #476823 reported by Andrew Pollock
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyinotify (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

pyinotify.Notifier.check_events() no longer takes any parameters, but the docstring suggests that it should.

pydoc from Hardy

pyinotify.Notifier.check_events = check_events(self, timeout=4000) unbound pyinotify.Notifier method
    Check for new events available to read, blocks up to timeout
    milliseconds.

    @param timeout: The timeout is passed on to select.poll(), thus
                    timeout=0 means 'return immediately', timeout>0
                    means 'wait up to timeout milliseconds' and
                    timeout=None means 'wait eternally', i.e. block.
    @type timeout: int
    @return: New events to read.
    @rtype: bool

pydoc from Karmic

pyinotify.Notifier.check_events = check_events(self) unbound pyinotify.Notifier method
    Check for new events available to read, blocks up to timeout
    milliseconds.

    @return: New events to read.
    @rtype: bool

Revision history for this message
Andrew Pollock (apollock) wrote :
Revision history for this message
Andrew Pollock (apollock) wrote :

This doesn't look to be a problem in version 0.8.7

Revision history for this message
Jonathan Davies (jpds) wrote :

This has been fixed in Lucid.

Changed in pyinotify (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.