This file is indexed.

/usr/lib/python2.7/dist-packages/watchdog-0.8.3.egg-info/PKG-INFO is in python-watchdog 0.8.3-2.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
Metadata-Version: 1.1
Name: watchdog
Version: 0.8.3
Summary: Filesystem events monitoring
Home-page: http://github.com/gorakhargosh/watchdog
Author: Yesudeep Mangalapilly
Author-email: yesudeep@gmail.com
License: Apache License 2.0
Description: Watchdog
        ========
        Python API and shell utilities to monitor file system events.
        
        
        Example API Usage
        -----------------
        A simple program that uses watchdog to monitor directories specified
        as command-line arguments and logs events generated:
            
        .. code-block:: python
        
            import sys
            import time
            import logging
            from watchdog.observers import Observer
            from watchdog.events import LoggingEventHandler
        
            if __name__ == "__main__":
                logging.basicConfig(level=logging.INFO,
                                    format='%(asctime)s - %(message)s',
                                    datefmt='%Y-%m-%d %H:%M:%S')
                path = sys.argv[1] if len(sys.argv) > 1 else '.'
                event_handler = LoggingEventHandler()
                observer = Observer()
                observer.schedule(event_handler, path, recursive=True)
                observer.start()
                try:
                    while True:
                        time.sleep(1)
                except KeyboardInterrupt:
                    observer.stop()
                observer.join()
        
        
        Shell Utilities
        ---------------
        Watchdog comes with a utility script called ``watchmedo``.
        Please type ``watchmedo --help`` at the shell prompt to
        know more about this tool.
        
        Here is how you can log the current directory recursively
        for events related only to ``*.py`` and ``*.txt`` files while
        ignoring all directory events:
            
        .. code-block:: bash
        
            watchmedo log \
                --patterns="*.py;*.txt" \
                --ignore-directories \
                --recursive \
                .
        
        You can use the ``shell-command`` subcommand to execute shell commands in
        response to events:
            
        .. code-block:: bash
        
            watchmedo shell-command \
                --patterns="*.py;*.txt" \
                --recursive \
                --command='echo "${watch_src_path}"' \
                .
        
        Please see the help information for these commands by typing:
        
        .. code-block:: bash
        
            watchmedo [command] --help
        
        
        About ``watchmedo`` Tricks
        ~~~~~~~~~~~~~~~~~~~~~~~~~~
        ``watchmedo`` can read ``tricks.yaml`` files and execute tricks within them in
        response to file system events. Tricks are actually event handlers that
        subclass ``watchdog.tricks.Trick`` and are written by plugin authors. Trick
        classes are augmented with a few additional features that regular event handlers
        don't need.
        
        An example ``tricks.yaml`` file:
            
        .. code-block:: yaml
        
            tricks:
            - watchdog.tricks.LoggerTrick:
                patterns: ["*.py", "*.js"]
            - watchmedo_webtricks.GoogleClosureTrick:
                patterns: ['*.js']
                hash_names: true
                mappings_format: json                  # json|yaml|python
                mappings_module: app/javascript_mappings
                suffix: .min.js
                compilation_level: advanced            # simple|advanced
                source_directory: app/static/js/
                destination_directory: app/public/js/
                files:
                  index-page:
                  - app/static/js/vendor/jquery*.js
                  - app/static/js/base.js
                  - app/static/js/index-page.js
                  about-page:
                  - app/static/js/vendor/jquery*.js
                  - app/static/js/base.js
                  - app/static/js/about-page/**/*.js
        
        The directory containing the ``tricks.yaml`` file will be monitored. Each trick
        class is initialized with its corresponding keys in the ``tricks.yaml`` file as
        arguments and events are fed to an instance of this class as they arrive.
        
        Tricks will be included in the 0.5.0 release. I need community input about them.
        Please file enhancement requests at the `issue tracker`_.
        
        
        Installation
        ------------
        Installing from PyPI using ``pip``:
            
        .. code-block:: bash
        
            $ pip install watchdog
        
        Installing from PyPI using ``easy_install``:
            
        .. code-block:: bash
        
            $ easy_install watchdog
        
        Installing from source:
            
        .. code-block:: bash
        
            $ python setup.py install
        
        
        Installation Caveats
        ~~~~~~~~~~~~~~~~~~~~
        The ``watchmedo`` script depends on PyYAML_ which links with LibYAML_,
        which brings a performance boost to the PyYAML parser. However, installing
        LibYAML_ is optional but recommended. On Mac OS X, you can use homebrew_
        to install LibYAML:
        
        .. code-block:: bash
        
            $ brew install libyaml
        
        On Linux, use your favorite package manager to install LibYAML. Here's how you
        do it on Ubuntu:
            
        .. code-block:: bash
        
            $ sudo aptitude install libyaml-dev
        
        On Windows, please install PyYAML_ using the binaries they provide.
        
        Documentation
        -------------
        You can browse the latest release documentation_ online.
        
        Contribute
        ----------
        Fork the `repository`_ on GitHub and send a pull request, or file an issue
        ticket at the `issue tracker`_. For general help and questions use the official
        `mailing list`_ or ask on `stackoverflow`_ with tag `python-watchdog`.
        
        Create and activate your virtual environment, then::
        
            pip install pytest
            pip install -e .
            py.tests tests
        
        
        Supported Platforms
        -------------------
        * Linux 2.6 (inotify)
        * Mac OS X (FSEvents, kqueue)
        * FreeBSD/BSD (kqueue)
        * Windows (ReadDirectoryChangesW with I/O completion ports;
          ReadDirectoryChangesW worker threads)
        * OS-independent (polling the disk for directory snapshots and comparing them
          periodically; slow and not recommended)
        
        Note that when using watchdog with kqueue, you need the
        number of file descriptors allowed to be opened by programs
        running on your system to be increased to more than the
        number of files that you will be monitoring. The easiest way
        to do that is to edit your ``~/.profile`` file and add
        a line similar to::
        
            ulimit -n 1024
        
        This is an inherent problem with kqueue because it uses
        file descriptors to monitor files. That plus the enormous
        amount of bookkeeping that watchdog needs to do in order
        to monitor file descriptors just makes this a painful way
        to monitor files and directories. In essence, kqueue is
        not a very scalable way to monitor a deeply nested
        directory of files and directories with a large number of
        files.
        
        About using watchdog with editors like Vim
        ------------------------------------------
        Vim does not modify files unless directed to do so.
        It creates backup files and then swaps them in to replace
        the files you are editing on the disk. This means that
        if you use Vim to edit your files, the on-modified events
        for those files will not be triggered by watchdog.
        You may need to configure Vim to appropriately to disable
        this feature.
        
        
        Dependencies
        ------------
        1. Python 2.6 or above.
        2. pathtools_
        3. select_backport_ (select.kqueue replacement for 2.6 on BSD/Mac OS X)
        4. XCode_ (only on Mac OS X)
        5. PyYAML_ (only for ``watchmedo`` script)
        6. argh_ (only for ``watchmedo`` script)
        
        
        Licensing
        ---------
        Watchdog is licensed under the terms of the `Apache License, version 2.0`_.
        
        Copyright 2011 `Yesudeep Mangalapilly`_.
        
        Copyright 2012 Google, Inc.
        
        Project `source code`_ is available at Github. Please report bugs and file
        enhancement requests at the `issue tracker`_.
        
        Why Watchdog?
        -------------
        Too many people tried to do the same thing and none did what I needed Python
        to do:
        
        * pnotify_
        * `unison fsmonitor`_
        * fsmonitor_
        * guard_
        * pyinotify_
        * `inotify-tools`_
        * jnotify_
        * treewalker_
        * `file.monitor`_
        * pyfilesystem_
        
        .. links:
        .. _Yesudeep Mangalapilly: yesudeep@gmail.com
        .. _source code: http://github.com/gorakhargosh/watchdog
        .. _issue tracker: http://github.com/gorakhargosh/watchdog/issues
        .. _Apache License, version 2.0: http://www.apache.org/licenses/LICENSE-2.0
        .. _documentation: http://packages.python.org/watchdog/
        .. _stackoverflow: http://stackoverflow.com/questions/tagged/python-watchdog
        .. _mailing list: http://groups.google.com/group/watchdog-python
        .. _repository: http://github.com/gorakhargosh/watchdog
        .. _issue tracker: http://github.com/gorakhargosh/watchdog/issues
        
        .. _homebrew: http://mxcl.github.com/homebrew/
        .. _select_backport: http://pypi.python.org/pypi/select_backport
        .. _argh: http://pypi.python.org/pypi/argh
        .. _PyYAML: http://www.pyyaml.org/
        .. _XCode: http://developer.apple.com/technologies/tools/xcode.html
        .. _LibYAML: http://pyyaml.org/wiki/LibYAML
        .. _pathtools: http://github.com/gorakhargosh/pathtools
        
        .. _pnotify: http://mark.heily.com/pnotify
        .. _unison fsmonitor: https://webdav.seas.upenn.edu/viewvc/unison/trunk/src/fsmonitor.py?view=markup&pathrev=471
        .. _fsmonitor: http://github.com/shaurz/fsmonitor
        .. _guard: http://github.com/guard/guard
        .. _pyinotify: http://github.com/seb-m/pyinotify
        .. _inotify-tools: http://github.com/rvoicilas/inotify-tools
        .. _jnotify: http://jnotify.sourceforge.net/
        .. _treewalker: http://github.com/jbd/treewatcher
        .. _file.monitor: http://github.com/pke/file.monitor
        .. _pyfilesystem: http://code.google.com/p/pyfilesystem
        
        
        .. :changelog:
        
        API changes
        -----------
        
        0.8.2
        ~~~~~
        
        - Event emitters are no longer started on schedule if ``Observer`` is not
          already running.
        
        
        0.8.0
        ~~~~~
        
        - ``DirectorySnapshot``: methods returning internal stat info replaced by
          ``mtime``, ``inode`` and ``path`` methods.
        - ``DirectorySnapshot``: ``walker_callback`` parameter deprecated.
        
Keywords: python filesystem monitoring monitor FSEvents kqueue inotify ReadDirectoryChangesW polling DirectorySnapshot
Platform: UNKNOWN
Classifier: Development Status :: 3 - Alpha
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: System Administrators
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Natural Language :: English
Classifier: Operating System :: POSIX :: Linux
Classifier: Operating System :: MacOS :: MacOS X
Classifier: Operating System :: POSIX :: BSD
Classifier: Operating System :: Microsoft :: Windows :: Windows NT/2000
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: C
Classifier: Topic :: Software Development :: Libraries
Classifier: Topic :: System :: Monitoring
Classifier: Topic :: System :: Filesystems
Classifier: Topic :: Utilities