node.ext.directory 0.5.3

Filesystem directory abstraction based on nodes

node.ext.directory

Filesystem directory abstraction based on nodes.

Usage

write me (or read tests)

Contributors

• Robert Niederreiter <rnix [at] squarewave [dot] at>

Changes

0.5.3

• Remove deleted keys from internal reference after __call__ in order to return the correct result when adding a file or directory with the same key again. [rnix, 2015-07-20]

0.5.2

• Use try/except instead of iteration to check whether directory child already in memory. [rnix, 2015-05-12]

0.5.1

• Always use os.chmod for setting directory permissions, not only if already exists. [rnix, 2015-03-03]

0.5

• Introduce fs_mode on directories and files. [rnix, 2015-03-03]

0.4

• Return empty list in File.lines if no data. [rnix, 2015-02-18]

• Consider filesystem encoding. Defaults to UTF-8. [rnix, 2015-02-18]

• Tree locking on modification. [rnix, 2014-09-02]

• Prevent empty keys in __setitem__. [rnix, 2014-09-02]

• Use plumbing decorator. [rnix, 2014-08-25]

0.3

• introduce default_file_factory on directories for controlling default file child creation. [rnix, 2013-12-09]

• move file logic in FileStorage behavior. [rnix, 2013-08-06]

• make file_factories a class property on directory storage. [rnix, 2013-08-06]

• make ignores a class property on directory storage. [rnix, 2013-08-06]

• Cleanup interfaces. [rnix, 2013-08-06]

0.2

• Almost complete rewrite. Fits now paradigms of node based API’s. [rnix, 2012-01-30]

0.1

• initial

License

Copyright (c) 2010-2015, BlueDynamics Alliance, Austria All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

• Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

• Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

• Neither the name of the BlueDynamics Alliance nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY BlueDynamics Alliance AS IS AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BlueDynamics Alliance BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.