fuse-python-0.2.1/0000755000175000017500000000000011361441047013016 5ustar spingspingfuse-python-0.2.1/Changelog0000644000175000017500000005253311361441047014640 0ustar spingsping2010-04-14 22:09 +0000 hartwork (c490d831ae11TAGS: 0.2.1 ) * make_release.sh: Fix generation of MANIFEST.in in make_release.sh (tested against hg 1.5.1) 2010-04-14 00:36 +0000 hartwork (c020e4b55af4) * fuse.py, fuseparts/__init__.py: Fix previous fix for ctors of Timespec and Flock to be backwards compatible, bump version to 0.2.1 2009-04-19 04:35 +0000 dzsekijo (35c03a19c703) * fuseparts/_fusemodule.c: Fix incorrect handling of getxattr for the size=0 case Report/fix by Facundo Batista, via Sebastien Delafond, cf. https://bugs.launchpad.net/ubuntu/+source/python-fuse/+bug/325860 2008-08-29 11:58 +0000 dzsekijo (c00f5e77a9c4) * fuse.py: absolutify the mount path when "fetch_mp" is set 2008-04-24 14:52 +0000 dzsekijo (23eee8905dd0) * fuseparts/_fusemodule.c: Make the "fetchattr_soft" macro tolerate if the value of the given attribute is None. This fixes the issue that returning an instance created by os.stat_result() from the "getattr" method caused EINVAL. Issue was reported by Forest Bond. 2008-02-05 14:13 +0000 dzsekijo (b8a0b93a5f38) * fuseparts/_fusemodule.c: Handle fsdestroy() vs. threading issue more sensibly than it was in 6dde0b0ad433. Now fsdestroy() works both when it's called as a DESTROY handler and when it's called within the lib's final clean-up. 2008-01-23 19:32 +0000 dzsekijo (9cf98e5e74c8) * fuse.py: fix some FuseStruct initializations 2007-12-11 15:17 +0000 dzsekijo (6dde0b0ad433) * fuseparts/_fusemodule.c: Remove Python locks from the destroy method. Deadlock issue was reported by Forest Bond. NOTES: These locks were undisputedly bogus as the point when destroy is called is out of the scope where Python locking is set up. Removing them and doing nothing more (as it's done now) is also OK if we assume that the module is used for writing a standalone program where thread management is completely handled by the fuse library -- as in this case the lib will ensure that there will be only one thread when the destroy method is called. However, this way: - We rely on an implementation detail of the lib. - If the Python fuse module is intended to be used in a "library fashion", ie. as a part of a more complex program where threads are created apart from the fuselib ones, then the locks might be needed for destroy. Anyway, I couldn't really extend the scope of Python locking in a way that embraces destroy's invocation and actually works, so I stick with simply removing those locks for now. 2007-06-29 21:46 +0200 toor (221d0a3816cb) * .hgtags: Added tag 0.2 for changeset 7d014ec0dc2bd3be2edf8e65c05f78665812ebc9 2007-06-29 19:45 +0000 dzsekijo (7d014ec0dc2bTAGS: 0.2 ) * fuseparts/__init__.py: bump version 2007-06-29 19:37 +0000 dzsekijo (672c835f58bd) * FAQ, README.new_fusepy_api: minor doc fixes 2007-06-24 23:08 +0000 dzsekijo (be075a630d06) * fuse.py: the FuseStat initializatior sets a default zero value for some of the stat fields 2007-06-18 15:04 +0000 dzsekijo (3da701e0688b) * fuse.py: check if fuse_python_api value is suitable (not just the presence of a value!) 2007-06-17 21:00 +0000 dzsekijo (bfe709f63c9c) * fuse.py: fix bug in previous commit 2007-06-17 20:29 +0000 dzsekijo (ba300811c040) * fuse.py: Define the required fields in FuseStruct derivatives to None if there is no explicit default value. This helps users to know what fields are there to be assigned, and makes it possible to iterate over the fields. 2007-06-15 23:25 +0000 dzsekijo (92f3f49abbc5) * fuseparts/_fusemodule.c: fix side-effecty attribute access from C which bogusly set PyErr_Occurred() 2007-05-18 16:55 +0200 toor (709843241f8f) * .hgtags: Added tag 0.2-pre3 for changeset 104a16a228e290552d06da27f0a8d01f70c59ff1 2007-05-18 14:48 +0000 dzsekijo (104a16a228e2TAGS: 0.2-pre3 ) * make_release.sh: further distribution streamlinining #4 2007-05-18 14:23 +0000 dzsekijo (c7aa95b16e32) * fuseparts/__init__.py: bump version 2007-05-18 14:21 +0000 dzsekijo (eed82fa7d1f9) * example/hello.py, example/xmp.py, fuse.py: defining fuse_python_api made mandatory 2007-05-18 13:54 +0000 dzsekijo (059f5a11a459) * make_release.sh: further distribution streamlinining #3 2007-05-18 13:47 +0000 dzsekijo (b9f2cdc99fe5) * MANIFEST.in: deleted file. * MANIFEST.in: further distribution streamlinining cont'd 2007-05-18 13:43 +0000 dzsekijo (5dc3a0165a72) * example/_find_fuse_parts.py, example/hello.py, example/xmp.py, make_release.sh: further distribution streamlinining 2007-05-15 23:55 +0200 toor (3019933a7a06) * .hgtags: Added tag 0.2-pre2 for changeset 488baa0b9517062131e17a3d24634b737f7dc733 2007-05-15 21:55 +0000 dzsekijo (488baa0b9517TAGS: 0.2-pre2 ) * fuseparts/__init__.py: bump version 2007-05-15 21:52 +0000 dzsekijo (f5f992f55b74) * README.1st: streamline README the 1st 2007-05-15 21:47 +0000 dzsekijo (5e3390e7f3e1) * make_release.sh: new file. * make_release.sh: automated the process of creating a release 2007-05-15 17:46 +0000 dzsekijo (733c85179e58) * MANIFEST.in, README.package_maintainers, util/voidspace-fusepy.css: new file. * AUTHORS, MANIFEST.in, README.1st, README.package_maintainers, setup.py, util/voidspace-fusepy.css: Meta files face lift. - Speak directly to package maintainers about compat issues - Miklos Szeredi deserves to be in AUTHORS - Also add Changelog and README.new_fusepy_api.html to source distro (ie. 'setup.py sdist' result) 2007-05-15 13:53 +0000 dzsekijo (74478f369763) * fuse.py: random docstring fixes 2007-05-15 13:40 +0000 dzsekijo (66d7b96c3f36) * setup.py: make setup.py PyPI compatible 2007-05-15 00:58 +0200 toor (9f76415848f6) * .hgtags: new file. * .hgtags: Added tag 0.2-pre1 for changeset 3f591e4a83c535c266a787e3771d500a5a1a8726 2007-05-14 22:56 +0000 dzsekijo (3f591e4a83c5TAGS: 0.2-pre1 ) * fuseparts/__init__.py: make version string adhere to FUSE versioning conventions 2007-05-14 22:43 +0000 dzsekijo (4257a80a048f) * setup.py: add support for Python egg creation 2007-05-11 13:23 +0000 dzsekijo (7d728c9abc8d) * README.new_fusepy_api, example/xmp.py, fuse.py, fuseparts/_fusemodule.c: added support for utimens and bmap methods 2007-05-11 09:41 +0000 dzsekijo (3c311ed1fd7e) * fuseparts/_fusemodule.c: use the dedicated size_t value builder if Python supports it (version >= 2.5.0) 2007-05-07 23:17 +0000 dzsekijo (9b596857988e) * README.1st, util/fusepychangelog.tmpl: minor meta fixes 2007-05-07 21:46 +0000 dzsekijo (5f04bdc6158a) * example/xmp.py, fuse.py, fuseparts/_fusemodule.c: add support for advisory locking ("lock" filesystem method) 2007-05-07 21:28 +0000 dzsekijo (2b187d6cbe6a) * fuse.py: refactor the classes representing system structures 2007-05-07 21:03 +0000 dzsekijo (2d6a424a1ff8) * example/xmp.py: Fix flush and fsync in xmp.py. - Don't call file.flush() if file is not open for writing (a fix for OS-es which adhere more to POSIX than Linux in this respect, eg. *BSD). - Do call file.flush() both from both of fsync and flush methods because data is to be flushed out from userspace cache anyway before we can go on. 2007-05-02 23:10 +0000 dzsekijo (512466bc2226) * README.1st, util/fusepychangelog.tmpl: new file. * ChangeLog: deleted file. * ChangeLog, README.1st, util/fusepychangelog.tmpl: get rid of handcrafted ChangeLog 2007-05-01 15:21 +0000 dzsekijo (d7c16bf5bc05) * fuseparts/_fusemodule.c: delete leaked in junk code 2007-05-01 15:04 +0000 dzsekijo (c1d7570d42cd) * ChangeLog, README.new_fusepy_api, fuse.py, fuseparts/_fusemodule.c: make keep_cache and direct_io settable filewise 2007-03-13 12:34 +0000 dzsekijo (d1e255d900e0) * ChangeLog, fuseparts/_fusemodule.c: check for float stat fields everywhere, not only on OS X 2007-02-27 17:50 +0000 dzsekijo (0f1b88025104) * ChangeLog, FAQ: document file class inistantiation via OPEN vs. via CREATE 2007-02-24 01:55 +0000 dzsekijo (ad3312c955ca) * ChangeLog, fuseparts/_fusemodule.c: Handle float stat fields of OS X. Patch based on code by Paul Fredrickson. 2007-01-18 23:13 +0000 dzsekijo (cc3a99b21a0d) * ChangeLog, fuseparts/_fusemodule.c: fix memory leak in FuseGetContext() 2006-12-14 09:45 +0000 dzsekijo (6e369309061e) * ChangeLog, fuseparts/_fusemodule.c: Clean up header inclusions. Assisted by Eric Evans. 2006-12-13 08:29 +0000 dzsekijo (1ff5b9f76e3c) * ChangeLog, fuseparts/_fusemodule.c: hush some warnings 2006-12-12 17:44 +0000 dzsekijo (0d1f8d1eae07) * ChangeLog, fuseparts/_fusemodule.c, setup.py: clean up threading related code a bit, let module be compiled for Pythons with no threading support 2006-12-11 21:40 +0000 dzsekijo (0ce90746c63d) * ChangeLog, fuseparts/_fusemodule.c: Move Python locking into method handlers in order to avoid LORs. Bug reported by Eric Evans. Fix based on idea and code from Miklos Szeredi. 2006-11-30 13:10 +0000 dzsekijo (91815ac716d9) * ChangeLog, fuseparts/_fusemodule.c: further refinements on Py -> C conversion 2006-11-29 17:39 +0000 dzsekijo (e8a15cbdb696) * ChangeLog, fuseparts/_fusemodule.c: Fix bogus conversion from Python integer types to C ones when C-ifying system structures. Bug reported by David Loveall. 2006-10-14 20:48 +0000 dzsekijo (1435a49dbd16) * README.new_fusepy_api, fuse.py: announce version of the current API by means of FUSE_PYTHON_API_VERSION constant 2006-10-14 15:57 +0000 dzsekijo (c26ad4ee2ac5) * ChangeLog, README.new_fusepy_api, example/hello.py, example/xmp.py, fuse.py: make fuse-python API explicitly specifiable instead of just having a compat hook 2006-10-12 23:53 +0000 dzsekijo (117dee9eb29c) * ChangeLog, example/_find_fuse_parts.py: emit a more useful error message when examples fail to import fuse 2006-10-12 23:51 +0000 dzsekijo (85f8d5474c9c) * fuse.py: fix 2006-10-12 23:24 +0000 dzsekijo (e60148c77170) * ChangeLog, example/xmp.py, fuse.py, fuseparts/_fusemodule.c: added support for init and destroy FUSE operations 2006-08-29 10:44 +0000 dzsekijo (629c61b84a91) * FAQ: new file. * ChangeLog, FAQ: added FAQ 2006-07-20 07:36 +0000 dzsekijo (e04379b2c7a2) * ChangeLog, fuseparts/_fusemodule.c: Let user override FUSE_USE_VERSION. This might help in getting around problems with FUSE snapshots when the API is in motion. Based on report by Péter Szilágyi 2006-07-17 10:26 +0000 dzsekijo (e1f57b73714a) * fuseparts/setcompatwrap.py: new file. * ChangeLog, INSTALL, fuse.py, fuseparts/setcompatwrap.py, fuseparts/subbedopts.py: Resolve some Python 2.3 compatibility problems. Issues reported by Tienshiao Ma. 2006-06-19 23:13 +0000 dzsekijo (075e6977c270) * ChangeLog, example/xmp.py: nitpick about some subtleties in xmp.py 2006-06-19 22:54 +0000 dzsekijo (e721ed03bef4) * ChangeLog, fuseparts/_fusemodule.c: fix bogus signature upon `create' method invocation 2006-06-07 09:10 +0000 dzsekijo (089c6a510fd3) * fuse.py, fuseparts/subbedopts.py: Fix. - fix bug in parsing two-in-one options - make SubOptsHive (FuseArgs) string representation sorted 2006-06-07 08:18 +0000 dzsekijo (cb90dcca75e8) * ChangeLog, fuse.py: make Fuse.fuseoptref() detect "-o [foo]bar" like two-in-one options 2006-06-07 07:42 +0000 dzsekijo (61301fbcde2e) * ChangeLog, fuse.py, fuseparts/subbedopts.py: let user specify an alternative parser class/`-o' handler for Fuse 2006-06-06 22:24 +0000 dzsekijo (8689b8b289b2) * ChangeLog, example/hello.py, example/xmp.py, fuse.py: set True as the default value of the `fetch_mp' parser option 2006-06-06 20:19 +0000 dzsekijo (95cc59e5556e) * fuseparts/__init__.py, fuseparts/_fusemodule.c, fuseparts/subbedopts.py: new file. * _fusemeta.py, _fusemodule.c: deleted file. * ChangeLog, _fusemeta.py, _fusemodule.c, example/_find_fuse_parts.py, fuse.py, fuseparts/__init__.py, fuseparts/_fusemodule.c, fuseparts/subbedopts.py, setup.py: Restructured source tree / II.: - Created fuseparts package - -> fuseparts/subbedoptparse.py - _fusemeta.py -> fuseparts/__init__.py - _fusemodule.c -> fuseparts/_fusemodule.c 2006-06-06 18:47 +0000 dzsekijo (4203f705c02c) * INSTALL: fix out-of-date information in INSTALL 2006-06-06 18:39 +0000 dzsekijo (949399754dad) * README.historic, example/_find_fuse_parts.py, example/hello.py, example/xmp.py: new file. * README, xmp.py: deleted file. * AUTHORS, ChangeLog, INSTALL, README, README.historic, README.new_fusepy_api, _fusemodule.c, example/_find_fuse_parts.py, example/hello.py, example/xmp.py, fuse.py, xmp.py: Restructured source tree, updated docs/metainformation. Source tree changes: - README -> README.historic - xmp.py -> example/xmp.py - added example/hello.py (contributed by Andrew Straw) - added example/_find_fuse_parts.py (aux script) 2006-06-06 07:00 +0000 dzsekijo (1fbfda5f4d6b) * ChangeLog, INSTALL, README, README.new_fusepy_api: updated docs 2006-06-06 05:00 +0000 dzsekijo (b519cd385964) * ChangeLog, fuse.py: replace `foo.has_key(bar)' with `bar in foo' 2006-06-06 04:44 +0000 dzsekijo (8ef39b485ae1) * ChangeLog, fuse.py: add support for querying any fs method in feature requester 2006-06-06 01:13 +0000 dzsekijo (466d43dd9d10) * ChangeLog, fuse.py, xmp.py: Option parsing refactorization. - Generic suboption parsing code separated into a dedicated classes - Implement FUSE option parsing by subclassing the aforementioned classes 2006-06-05 00:04 +0000 dzsekijo (a654ef04d464) * fuse.py, xmp.py: some refinements in method naming and feature requesting 2006-06-04 22:45 +0000 dzsekijo (c7ca4cfab5aa) * ChangeLog, xmp.py: sanitize xmp.py methods 2006-06-04 19:51 +0000 dzsekijo (c39b74d70533) * fuse.py, xmp.py: Rewrite feature requesting interface. - rename functions: `feature_need' -> `feature_needs' and `feature_req' -> `feature_assert' - give a more robust and clean implementation 2006-06-04 17:37 +0000 dzsekijo (02c7643e7e28) * ChangeLog, _fusemodule.c, fuse.py, xmp.py: added interface for retrieving FUSE API version and requiring features from the underlying library 2006-06-04 14:35 +0000 dzsekijo (d5da0b1739b2) * ChangeLog, _fusemodule.c, fuse.py, xmp.py: Added support for the rest of FUSE methods. (flush, fgetattr, ftruncate, access, getxattr, listxattr, setxattr, removexattr) 2006-06-01 15:14 +0000 dzsekijo (9a242cf24697) * _fusemodule.c: fix bogus termination of directory reading 2006-06-01 13:07 +0000 dzsekijo (8e83fb371afa) * ChangeLog, fuse.py: distillate Fuse instance -> method proxying code into a dedicated class 2006-06-01 08:20 +0000 dzsekijo (bf58eabe6cb4) * COPYING: new file. * COPYING: added licensing information 2006-05-31 21:43 +0000 dzsekijo (f3c75ff5097f) * ChangeLog, _fusemodule.c, fuse.py, xmp.py: Update code so that it can use newer FUSE features / II. Update directory related features: - Switch to readdir() from deprecated getdir() method. - Add support for new directory methods. - Make directory I/O stateful. - Extend OO wrappers to directories. - Switch from sequence based data transfer model to general - iterator based one. - Add a dedicated class to carry directory entries instead - of using tuples. - Add compact hooks. 2006-05-31 16:42 +0000 dzsekijo (0b9eb32c7bf6) * ChangeLog, README.new_fusepy_api, _fusemodule.c, fuse.py, xmp.py: Update code so that it can use newer FUSE features / I. Make file I/O stateful: - If `open' methods returns an object, that will be preserved and passed around to I/O requests on the file in question. - Added support for `create' method - Wrap this mechanism into OO: file I/O methods can be implemented via an user specified class. - Add warning to README.new_fusepy_api 2006-05-31 16:12 +0000 dzsekijo (1f1f1e69e5ae) * _fusemodule.c: fix a statfs compat bug 2006-05-31 14:07 +0000 dzsekijo (383534e25bd5) * ChangeLog, _fusemodule.c: fix stat/offset integer overflows 2006-05-29 21:53 +0000 dzsekijo (f5f23a4aa92a) * ChangeLog, _fusemodule.c, fuse.py: Compat layer related fixes. 2006-05-29 13:20 +0000 dzsekijo (6882690f6ada) * _fusemodule.c: one Py_DECREF was put at the wrong place... 2006-05-29 13:14 +0000 dzsekijo (ea2a25443d91) * ChangeLog, _fusemodule.c: add some missing Py_DECREF-s 2006-05-28 23:53 +0000 dzsekijo (ef4fd0328dd7) * ChangeLog, _fusemodule.c: Add support for st_rdev, st_blksize, st_block stat fields. Noticed by Robert Bradford. 2006-05-28 23:40 +0000 dzsekijo (9f86a81a5c2d) * README.new_fusepy_api, xmp.py: minor fixes 2006-05-28 13:56 +0000 dzsekijo (d264bf9d8eac) * ChangeLog, README.new_fusepy_api, _fusemodule.c, fuse.py, xmp.py: Switch getattr / statfs to an object oriented interface. 2006-05-27 18:58 +0000 dzsekijo (fd8517b6b70c) * ChangeLog, README.new_fusepy_api, _fusemodule.c, fuse.py, xmp.py: add os.statvfs() compatible statvfs method [mark statfs deprecated but keep working via a compat shim] 2006-05-27 11:40 +0000 dzsekijo (46b7014c97a3) * _fusemodule.c: Fix: require the fuse argvec to be a non-empty sequence and check it properly. 2006-05-27 09:06 +0000 dzsekijo (460f3dc9eceb) * xmp.py: fix typo in xmp.py 2006-05-27 08:04 +0000 dzsekijo (490859b1b83b) * README.new_fusepy_api: new file. * ChangeLog, README.new_fusepy_api, _fusemeta.py, _fusemodule.c, fuse.py, xmp.py: New Python API with enhanced commandline handling. 2006-05-27 07:23 +0000 dzsekijo (ec3f6efdc87c) * _fusemeta.py: new file. * ChangeLog, _fusemeta.py, fuse.py, setup.py: setup.py related fixes 2006-05-26 16:01 +0000 dzsekijo (3ff338399809) * ChangeLog, _fusemodule.c, fuse.py, setup.py, xmp.py: Syntax cleanup 2: fix indetation, uniformize look 2006-05-26 15:58 +0000 dzsekijo (4dd8bb8c6070) * code.leo: deleted file. * ChangeLog, README, _fusemodule.c, code.leo, fuse.py, xmp.py: Syntax cleanup 1: strip leo markup. 2006-05-24 05:04 +0000 dzsekijo (a2466ed1accd) * ChangeLog, _fusemodule.c, fuse.py, xmp.py: Revamp fs initialization code. 2006-05-23 20:00 +0000 dzsekijo (6b3b309d48e3) * _fusemodule.c: make use of library opts also when FUSE_VERSION >= 25 2006-05-23 18:23 +0000 dzsekijo (0f101358dd69) * _fusemodule.c: fix previous fix 2006-05-23 16:00 +0000 dzsekijo (a3a10e33bb5e) * ChangeLog, _fusemodule.c: result of argument type check was ignored in FuseInvalidate(), fix it 2006-05-23 07:08 +0000 dzsekijo (d58976cd74ea) * AUTHORS, ChangeLog, _fusemodule.c: Update code so that it can be compiled against FUSE libs with API from 21 to 26 2006-05-23 07:02 +0000 dzsekijo (72ca1670afa8) * Makefile: deleted file. * ChangeLog, Makefile, setup.py, xmp.py: Rebase build system on pkg-config. 2006-05-23 06:53 +0000 dzsekijo (825d24362f5f) * ChangeLog, xmp.py: Fix statfs index mismatch in xmp.py 2006-02-04 19:32 +0000 sdelafond (51056cf0f8e1) * ChangeLog, _fusemodule.c, fuse.py, xmp.py: * Removed unnecessary "st->st_ino = 0" line in _fusemodule.c. * Added __init__ argument handling in fuse.py. Command-line arguments still take precedence over contructor ones. * Removed unused os module from fuse.py. * Changed def read(self, path, length, offset) to def read(self, path, length, offset) so that len() can be used inside read(). 2005-09-19 00:43 +0000 sdelafond (d1299c647953) * _fusemodule.c, code.leo, fuse.py, xmp.py: Changed license from GPL to LGPL, after approval from Steven James and Jeff Epler. 2005-04-07 18:25 +0000 sdelafond (5293b014aa11) * AUTHORS, ChangeLog, _fusemodule.c: Added support for statfs.bavail so that df can correctly report disk usage. 2004-11-22 06:53 +0000 sdelafond (a6fd1d240a9a) * AUTHORS: Put Steven James name in, removed mine: his fixes are much cleaner than mine. 2004-11-22 01:40 +0000 sdelafond (6e12f1931f24) * AUTHORS, ChangeLog, INSTALL, setup.py: Took over maintainership. 2004-11-11 15:41 +0000 mszeredi (3f84c72d6872) * README: new file. * README: importing sources 2004-11-11 15:41 +0000 mszeredi (37c8c74dde9d) * AUTHORS, ChangeLog, INSTALL, Makefile, _fusemodule.c, code.leo, fuse.py, setup.py, xmp.py: new file. * AUTHORS, ChangeLog, INSTALL, Makefile, _fusemodule.c, code.leo, fuse.py, setup.py, xmp.py: Initial revision fuse-python-0.2.1/make_release.sh0000644000175000017500000000277411361440701015775 0ustar spingsping#!/bin/sh -e # Works only in the hg repo incarnation of the source tree. # Mercurial, docutils, setuptools needs to be installed. setupdotpy_version=`python setup.py -V` # Finding out Mercurial cset until which we want to log hgid=`hg id | awk '{print $1}'` if echo $hgid | grep -q '+$'; then echo "you have outstanding changes, don't make a release" >&2 exit 1 fi hgrev=`hg log --template '{node|short} {rev}\n' | awk "{if (\\$1 ~ /$hgid/) { print \\$2 }}"` hgtiprev=`hg log --template '{rev}' -r tip` if ! [ $hgrev -eq $hgtiprev ]; then (echo "*************" echo "Warning: you are making a release from an older state of the code!" echo "*************") >&2 fi if hg log --template '{tags}' -r $hgid | egrep -q "(^| )$setupdotpy_version($| )"; then log_to=$hgid elif [ $hgrev -gt 0 ] && hg log --template '{desc}' -r $hgid | grep -q "Added tag $setupdotpy_version for changeset" && hg log --template '{tags}' -r $(($hgrev - 1)) | egrep -q "(^| )$setupdotpy_version($| )"; then log_to=$(($hgrev - 1)) else echo "HG tag '$hg_tag' doesn't match reported program version '$setupdotpy_version'" >&2 exit 1 fi hg log --style util/fusepychangelog.tmpl -r $log_to:0 > Changelog rst2html.py --stylesheet util/voidspace-fusepy.css README.new_fusepy_api > README.new_fusepy_api.html { hg manif | grep -v '^\.' | sed 's/^[0-9]\{3,\} \+\(.\+\)$/\1/' ; echo Changelog ; echo README.new_fusepy_api.html ; } | sed 's/^/include /' > MANIFEST.in python setup.py sdist python setup.py bdist_egg fuse-python-0.2.1/PKG-INFO0000644000175000017500000000111611361441047014112 0ustar spingspingMetadata-Version: 1.0 Name: fuse-python Version: 0.2.1 Summary: Bindings for FUSE Home-page: http://fuse.sourceforge.net/wiki/index.php/FusePython Author: Csaba Henk Author-email: csaba.henk@creo.hu License: LGPL Description: UNKNOWN Platform: posix Classifier: Development Status :: 4 - Beta Classifier: Intended Audience :: Developers Classifier: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) Classifier: Operating System :: POSIX Classifier: Programming Language :: C Classifier: Programming Language :: Python Classifier: Topic :: System :: Filesystems fuse-python-0.2.1/FAQ0000644000175000017500000000302711361440701013346 0ustar spingsping========================= FUSE-Python_ bindings FAQ ========================= .. _FUSE-Python: http://fuse.sourceforge.net/wiki/index.php/FusePython :Author: Csaba Henk Frequently Asked Questions ========================== Compilation of ``fuseparts/_fusemodule.c`` fails with *error: too few arguments to function* -------------------------------------------------------------------------------------------- Most likely you have FUSE 2.6.0-pre2. Most likely you are on Gentoo. While fuse-py tries to work with as many API revisions as it's possible, the 2.6.0-pre2 release uses a half-baked state of API 26, which won't work with fuse-py. The same issue can occur if you use a CVS snapshot. Solutions: * Enforce the usage of a stabilized API (practically, API 25) with:: env CFLAGS=-DFUSE_USE_VERSION=25 python setup.py build * Upgrade your FUSE installation. As of writing this, 2.6.0-pre3 is available. When I use a dedicated file class, how can I tell apart the cases when an instance of it is instantiated from a ``CREATE`` callback and when it's instantiated from an ``OPEN`` callback? ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ If your file class is instantiated via ``FUSE_OPEN``, then it's ``__init__`` will be called with ``(path, flags)`` arguments. If your file class is instantiated via ``FUSE_CREATE``, then it's ``__init__`` will be called with ``(path, flags, mode)`` arguments. fuse-python-0.2.1/setup.cfg0000644000175000017500000000007311361441047014637 0ustar spingsping[egg_info] tag_build = tag_date = 0 tag_svn_revision = 0 fuse-python-0.2.1/setup.py0000644000175000017500000000735111361440701014532 0ustar spingsping# distutils build script # To install fuse-python, run 'python setup.py install' # This setup.py based on that of shout-python (py bindings for libshout, # part of the icecast project, http://svn.xiph.org/icecast/trunk/shout-python) try: from setuptools import setup from setuptools.dist import Distribution except ImportError: from distutils.core import setup from distutils.dist import Distribution from distutils.core import Extension import os import sys from fuseparts import __version__ classifiers = """\ Development Status :: 4 - Beta Intended Audience :: Developers License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) Operating System :: POSIX Programming Language :: C Programming Language :: Python Topic :: System :: Filesystems """ class MyDistribution(Distribution): """ Obnoxious hack to enforce the packager to generate the to-be-generated files """ def run_command(self, command): if command == 'sdist': for f in ('Changelog', 'README.new_fusepy_api.html'): if not os.path.exists(f): raise RuntimeError, 'file ' + `f` + \ " doesn't exist, please generate it before creating a source distribution" return Distribution.run_command(self, command) # write default fuse.pc path into environment if PKG_CONFIG_PATH is unset #if not os.environ.has_key('PKG_CONFIG_PATH'): # os.environ['PKG_CONFIG_PATH'] = '/usr/local/lib/pkgconfig' # Find fuse compiler/linker flag via pkgconfig if os.system('pkg-config --exists fuse 2> /dev/null') == 0: pkgcfg = os.popen('pkg-config --cflags fuse') cflags = pkgcfg.readline().strip() pkgcfg.close() pkgcfg = os.popen('pkg-config --libs fuse') libs = pkgcfg.readline().strip() pkgcfg.close() else: if os.system('pkg-config --usage 2> /dev/null') == 0: print """pkg-config could not find fuse: you might need to adjust PKG_CONFIG_PATH or your FUSE installation is very old (older than 2.1-pre1)""" else: print "pkg-config unavailable, build terminated" sys.exit(1) # there must be an easier way to set up these flags! iflags = [x[2:] for x in cflags.split() if x[0:2] == '-I'] extra_cflags = [x for x in cflags.split() if x[0:2] != '-I'] libdirs = [x[2:] for x in libs.split() if x[0:2] == '-L'] libsonly = [x[2:] for x in libs.split() if x[0:2] == '-l'] try: import thread except ImportError: # if our Python doesn't have thread support, we enforce # linking against libpthread so that libfuse's pthread # related symbols won't be undefined libsonly.append("pthread") # include_dirs=[] # libraries=[] # runtime_library_dirs=[] # extra_objects, extra_compile_args, extra_link_args fusemodule = Extension('fuseparts._fusemodule', sources = ['fuseparts/_fusemodule.c'], include_dirs = iflags, extra_compile_args = extra_cflags, library_dirs = libdirs, libraries = libsonly) # data_files = [] if sys.version_info < (2, 3): _setup = setup def setup(**kwargs): if kwargs.has_key("classifiers"): del kwargs["classifiers"] _setup(**kwargs) setup (name = 'fuse-python', version = __version__, description = 'Bindings for FUSE', classifiers = filter(None, classifiers.split("\n")), license = 'LGPL', platforms = ['posix'], url = 'http://fuse.sourceforge.net/wiki/index.php/FusePython', author = 'Jeff Epler', author_email = 'jepler@unpythonic.dhs.org', maintainer = 'Csaba Henk', maintainer_email = 'csaba.henk@creo.hu', ext_modules = [fusemodule], packages = ["fuseparts"], py_modules=["fuse"], distclass = MyDistribution) fuse-python-0.2.1/INSTALL0000644000175000017500000000337011361440701014046 0ustar spingspingREQUIREMENTS: - FUSE 2.* (tested with FUSE 2.3 and newer) - In general, Python 2.3 or newer. Version specific notes: - 2.4: this is the version the code is developed with, so you can expect this one to work the most smoothly. - 2.3: in general, it seems to be useable. However, the optparse module of Python 2.3 is out of date. This doesn't have fatal consequences, but if you want nice help optput / version info, you should either use optparse.py from 2.4 or install a recent version of Optik (http://optik.sourceforge.net) (and adjust the respective import statements to use optik instead of optparse). - 2.2: With some minor adjustments / additional imports it should be useable, too. If not else, you'll need to install Optik (see previous item) and add some "from __future__ import generators" statements. - pkg-config [http://pkgconfig.freedesktop.org/] Additional info about the Python requirement. INSTALLATION: The best way to install this python FUSE module is: 1. Type 'python setup.py build'. (If you have FUSE installed at a non-standard location, adjust the PKG_CONFIG_PATH environment variable accordingly.) 2. You might try the example filesystems under example/. Eg., see what "python example/xmp.py -h" gives. 3. If all has gone ok, become root and type 'python setup.py install'. That way, the FUSE python modules will be built against the correct version of python and installed in your system-wide python directory. This will allow your filesystem script to find them, no matter where it's residing. WARNING: We have altered from the original FUSE Python API in non-compatible ways. See README.new_fusepy_api how can you get running a fs which is written against the original API. fuse-python-0.2.1/README.package_maintainers0000644000175000017500000000051511361440701017657 0ustar spingspingThe API of the Python binding has changed with fuse-python 0.2-pre1. Therefore older fuse-python based filesystems *won't work* out of the box with fuse-python 0.2-pre1. However, no need to worry. Just read the *Old API/Enforcing compatibility* section of ``README.new_fusepy_api`` and you will know how to deal with the situation. fuse-python-0.2.1/COPYING0000644000175000017500000006350411361440701014055 0ustar spingsping GNU LESSER GENERAL PUBLIC LICENSE Version 2.1, February 1999 Copyright (C) 1991, 1999 Free Software Foundation, Inc. 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] Preamble The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below. When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things. To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it. For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights. We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library. To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others. Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license. Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs. When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library. We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances. For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License. In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system. Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library. The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run. GNU LESSER GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION 0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you". A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables. The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".) "Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does. 1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. 2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) The modified work must itself be a software library. b) You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change. c) You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License. d) If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful. (For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library. In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy. This option is useful when you wish to copy part of the code of the Library into a program that is not a library. 4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange. If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code. 5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License. However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables. When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law. If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.) Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself. 6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications. You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things: a) Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.) b) Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with. c) Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution. d) If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place. e) Verify that the user has already received a copy of these materials or that you have already sent this user a copy. For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute. 7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things: a) Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above. b) Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work. 8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. 9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it. 10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License. 11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation. 14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally. NO WARRANTY 15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Libraries If you develop a new library, and you want it to be of the greatest possible use to the public, we recommend making it free software that everyone can redistribute and change. You can do so by permitting redistribution under these terms (or, alternatively, under the terms of the ordinary General Public License). To apply these terms, attach the following notices to the library. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. Copyright (C) This library is free software; you can redistribute it and/or modify it under the terms of the GNU Lesser General Public License as published by the Free Software Foundation; either version 2.1 of the License, or (at your option) any later version. This library is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public License for more details. You should have received a copy of the GNU Lesser General Public License along with this library; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA Also add information on how to contact you by electronic and paper mail. You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the library, if necessary. Here is a sample; alter the names: Yoyodyne, Inc., hereby disclaims all copyright interest in the library `Frob' (a library for tweaking knobs) written by James Random Hacker. , 1 April 1990 Ty Coon, President of Vice That's all there is to it! fuse-python-0.2.1/MANIFEST.in0000644000175000017500000000107711361441047014561 0ustar spingspinginclude .hgtags include AUTHORS include COPYING include FAQ include INSTALL include README.1st include README.historic include README.new_fusepy_api include README.package_maintainers include example/_find_fuse_parts.py include example/hello.py include example/xmp.py include fuse.py include fuseparts/__init__.py include fuseparts/_fusemodule.c include fuseparts/setcompatwrap.py include fuseparts/subbedopts.py include make_release.sh include setup.py include util/fusepychangelog.tmpl include util/voidspace-fusepy.css include Changelog include README.new_fusepy_api.html fuse-python-0.2.1/fuse_python.egg-info/0000755000175000017500000000000011361441047017053 5ustar spingspingfuse-python-0.2.1/fuse_python.egg-info/top_level.txt0000644000175000017500000000001711361441047021603 0ustar spingspingfuse fuseparts fuse-python-0.2.1/fuse_python.egg-info/PKG-INFO0000644000175000017500000000111611361441047020147 0ustar spingspingMetadata-Version: 1.0 Name: fuse-python Version: 0.2.1 Summary: Bindings for FUSE Home-page: http://fuse.sourceforge.net/wiki/index.php/FusePython Author: Csaba Henk Author-email: csaba.henk@creo.hu License: LGPL Description: UNKNOWN Platform: posix Classifier: Development Status :: 4 - Beta Classifier: Intended Audience :: Developers Classifier: License :: OSI Approved :: GNU Library or Lesser General Public License (LGPL) Classifier: Operating System :: POSIX Classifier: Programming Language :: C Classifier: Programming Language :: Python Classifier: Topic :: System :: Filesystems fuse-python-0.2.1/fuse_python.egg-info/SOURCES.txt0000644000175000017500000000103611361441047020737 0ustar spingsping.hgtags AUTHORS COPYING Changelog FAQ INSTALL MANIFEST.in README.1st README.historic README.new_fusepy_api README.new_fusepy_api.html README.package_maintainers fuse.py make_release.sh setup.py example/_find_fuse_parts.py example/hello.py example/xmp.py fuse_python.egg-info/PKG-INFO fuse_python.egg-info/SOURCES.txt fuse_python.egg-info/dependency_links.txt fuse_python.egg-info/top_level.txt fuseparts/__init__.py fuseparts/_fusemodule.c fuseparts/setcompatwrap.py fuseparts/subbedopts.py util/fusepychangelog.tmpl util/voidspace-fusepy.cssfuse-python-0.2.1/fuse_python.egg-info/dependency_links.txt0000644000175000017500000000000111361441047023121 0ustar spingsping fuse-python-0.2.1/util/0000755000175000017500000000000011361441047013773 5ustar spingspingfuse-python-0.2.1/util/fusepychangelog.tmpl0000644000175000017500000000134311361440701020051 0ustar spingspingheader = '{date|shortdate} {author|person}\n{tags}\n' header_verbose = '' changeset = '\t* {files|stringify|fill68|tabindent}{desc|fill68|tabindent|strip}\n\t[{node|short}]\n\n' changeset_quiet = '\t* {desc|firstline|fill68|tabindent|strip}\n\n' changeset_verbose = '{date|isodate} {author|person} <{author|email}> ({node|short}{tags})\n\n\t* {file_adds|stringify|fill68|tabindent}{file_dels|stringify|fill68|tabindent}{files|stringify|fill68|tabindent}{desc|fill68|tabindent|strip}\n\n' start_tags = 'TAGS: ' tag = '{tag}, ' last_tag = '{tag}\n' file = '{file}, ' last_file = '{file}:\n\t' file_add = '{file_add}, ' last_file_add = '{file_add}: new file.\n* ' file_del = '{file_del}, ' last_file_del = '{file_del}: deleted file.\n* ' fuse-python-0.2.1/util/voidspace-fusepy.css0000644000175000017500000000470011361440701017770 0ustar spingsping/* :Authors: Ian Bicking, Michael Foord :Contact: fuzzyman@voidspace.org.uk :Date: 2005/08/26 :Version: 0.1.0 :Copyright: This stylesheet has been placed in the public domain. Stylesheet for Docutils. Based on ``blue_box.css`` by Ian Bicking and ``html4css1.css`` revision 1.46. */ @import url(html4css1.css); body { font-family: Arial, sans-serif; background-color: lightblue; } em, i { /* Typically serif fonts have much nicer italics */ font-family: Times New Roman, Times, serif; } a.target { color: blue; } a.target { color: blue; } a.toc-backref { text-decoration: none; color: black; } a.toc-backref:hover { background-color: inherit; } a:hover { background-color: #cccccc; } div.attention, div.caution, div.danger, div.error, div.hint, div.important, div.note, div.tip, div.warning { background-color: #cccccc; padding: 3px; width: 80%; } div.admonition p.admonition-title, div.hint p.admonition-title, div.important p.admonition-title, div.note p.admonition-title, div.tip p.admonition-title { text-align: center; background-color: #999999; display: block; margin: 0; } div.attention p.admonition-title, div.caution p.admonition-title, div.danger p.admonition-title, div.error p.admonition-title, div.warning p.admonition-title { color: #cc0000; font-family: sans-serif; text-align: center; background-color: #999999; display: block; margin: 0; } h1, h2, h3, h4, h5, h6 { font-family: Helvetica, Arial, sans-serif; border: thin solid black; /* This makes the borders rounded on Mozilla, which pleases me */ -moz-border-radius: 8px; padding: 4px; } h1 { background-color: #444499; color: #ffffff; border: medium solid black; } h1 a.toc-backref, h2 a.toc-backref { color: #ffffff; } h2 { background-color: #666666; color: #ffffff; border: medium solid black; } h3, h4, h5, h6 { background-color: #cccccc; color: #000000; } h3 a.toc-backref, h4 a.toc-backref, h5 a.toc-backref, h6 a.toc-backref { color: #000000; } h1.title { text-align: center; background-color: pink; color: #eeeeee; border: thick solid black; -moz-border-radius: 20px; } table.footnote { padding-left: 0.5ex; } table.citation { padding-left: 0.5ex } pre.literal-block, pre.doctest-block { border: thin black solid; padding: 5px; } .image img { border-style : solid; border-width : 2px; } h1 tt, h2 tt, h3 tt, h4 tt, h5 tt, h6 tt { font-size: 100%; } code, tt { color: #000066; } fuse-python-0.2.1/README.historic0000644000175000017500000000664111361440701015524 0ustar spingspingWARNING: THIS FILE DOESN'T MATCH CURRENT STATE OF THE AFFAIRS. Refer to the INSTALL file for build/install instructions General Information =================== This is a Python[1] interface to FUSE[2]. FUSE (Filesystem in USErspace) is a simple interface for userspace programs to export a virtual filesystem to the linux kernel. FUSE also aims to provide a secure method for non privileged users to create and mount their own filesystem implementations. When run from the commandline, "fuse.py" simply reexports the root filesystem within the mount point as example/fusexmp does in the main FUSE distribution. It also offers a class, fuse.Fuse, which can be subclassed to create a filesystem. fuse.Xmp is the example filesystem implementation. In your subclass of fuse, add attributes with the expected names ("getattr", "readlink", etc) and call signatures (refer to fuse.Xmp) then call main(). Make it runnable as a #! script, and mount with fusermount