Pyxattr

Latest version: v0.8.1

Safety actively analyzes 628903 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 3

0.5.1

*released Wed, 16 May 2012*

Bug-fix release. Thanks to Dave Malcolm and his cpychecker tool, a
number of significant bugs (refcount leaks and potential NULL-pointer
dereferences) have been fixed.

Furthermore, compatibility with Python 3 has been improved; this however
required changing the meaning of the ``namespace`` argument to the
functions: if passed, None is no longer a valid value; pass an empty
string if (due to the structure of your program) you have to pass this
argument but want to specify no namespace.

Also, the project home page has changed from SourceForge to GitHub, and
the documentation has been converted from epydoc-based to sphinx.

0.5

*released Sun, 27 Dec 2009*

Implemented support for Python 3. This required a significant change to
the C module, hence the new version number.

0.4

*released Mon, 30 Jun 2008*

API

The old functions ({get,set,list,remove}xattr) are deprecated and replaced with
a new API that is namespace-aware and hopefully will allow other OSes (e.g.
FreeBSD) to be supported more naturally.

Both the old and the new API are supported in the 0.4 versions, however users
are encouraged to migrate to the new API.

New features

A new bulk get function called get_all() has been added that should be somewhat
faster in case of querying files which have many attributes.

License

Since LGPLv3 is not compatible with GPLv2 (which unfortunately I didn't realize
before), the license was changed to LGPLv2.1 or later.

Internals

Unittest coverage was improved.

0.3

*released Sun, 09 Mar 2008*

* changed licence from GPL to LGPL (3 or later)
* changed listxattr return type from tuple to a list
* developer-related: added unittests

0.2.2

*released Sun, 01 Jul 2007*

* fixed listing symlink xattrs

0.2.1

*released Sat, 11 Feb 2006*

* fixed a bug when reading symlink EAs (you weren't able to
do it, actually)
* fixed a possible memory leak when the actual read of the EA
failed but the call to get the length of the EA didn't

Page 3 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.