Parse, validate and reformat standard numbers and codes.
This library offers functions for parsing, validating and reformatting standard numbers and codes in various formats.
Alan Coopersmith (1):
XORG_COMPILER_FLAGS: Add -Wlogical-op to default warning set
Arnaud Fontaine (1):
Add XORG_WITH_M4 macro
Gaetan Nadon (3):
Bump minimum Autoconf required version to 2.62
Provide the automake INSTALL file at level 1.11
Version bump: 1.19.0
Hans de Goede (1):
XORG_PROG_RAWCPP: Add TRADITIONALCPPFLAGS
This minor bugfix release restores the ability to disconnect
providers from each other using "0x0" as the provider XID. For
example, to disconnect a display offload sink from its source,
use
xrandr --setprovideroutputsource <sink> 0x0
This release also formats the GUID provided by DisplayPort 1.2
displays in traditional GUID form.
Finally, this release increases the precision of refresh rate
calculations to disambiguate modes with very similar refresh
rates and to improve the accuracy for interlaced modes.
Aaron Plattner (5):
Split output property printing into a helper function
Move EDID printing into a helper function
Special-case printing of the GUID property
xrandr: document how to disconnect RandR 1.4 providers
xrandr 1.4.2
Dave Airlie (1):
xrandr: allow disconnecting of offload and outputs
Ville Syrjälä (2):
xrandr: Use more decimal places when printing various rates
xrandr: Use floating point for VTotal when calculating refresh rate
Version 6.2.11 - March 12 2014
[CHANGES]
New facilities:
o global: New -S (--scope) <directory> option. This option prints only tags
which exist under <directory>. It is similar to the -l option, but different
from it in that you need not change directory.
o gtags: Now, the skip list allows glob file patterns (*, ?, [...], [!...], [^...]).
o gtags.conf: Added the following glob patterns to the skip list:
*.orig,*.rej,*.bak,*~,#*#,*.swp,*.tmp,*_flymake.*,*_flymake
o gtags: Now, the -I option supports file list (-f option or gtags.files).
Instead, idutils 4.5 or later is required.
[FIXED BUGS]
o global: With combination of the --invert-match and --literal, it does not match
the last line of files. Now it works.
o global: Literal search with the -i option prints an unmatched tag in a certain
kind of case. Now it works.
o global: 'global -cI' without argument causes segmentation fault.
Now it works.
libmikmod v3.3.6 was released on 20-Mar-2014.
- UMX loader: Minor corrections to the container parse code with
relation to upkg file format. (for correctness' sake only...)
- ALSA and ESD drivers: Fixed a dlopen() issue.
- PulseAudio driver: Simplified its command line parser procedure,
so that it always sets server and sink to some value, NULL or
otherwise, and fix a very minor memory leak on some occasions.
- Configury, OSS driver: Removed useless check for /dev/sndstat
presence, added <soundcard.h> check to cover all our bases for
less common setups.
- Configury, NAS driver: Use the configury detected X header and
library locations when necessary, not just hardcoded /usr/X11R6/.
- Several configury and makefile clean-ups.
- Added Dreamcast driver from the old 3.2.0b2 dreamcast.es port.
Overview of changes leading to 0.9.27
Tuesday, March 18, 2014
=====================================
- Don't use "register" storage class specifier
- Wrap definition of free_langs() with HAVE_ATEXIT
- Add coretext_aat shaper and hb_coretext_face_create() constructor
- If HAVE_ICU_BUILTIN is defined, use hb-icu Unicode callbacks
- Add Myanmar test case from OpenType Myanmar spec
- Only do fallback Hebrew composition if no GPOS 'mark' available
- Allow bootstrapping without gtk-doc
- Use AM_MISSING_PROG for ragel and git
- Typo in ucdn's Makefile.am
- Improve MemoryBarrier() implementation
FFTW 3.3.4
* New functions fftw_alignment_of (to check whether two arrays are
equally aligned for the purposes of applying a plan) and fftw_sprint_plan
(to output a description of plan to a string).
* Bugfix in fftw-wisdom-to-conf; thanks to Florian Oppermann for the
bug report.
* Fixed manual to work with texinfo-5.
* Increased timing interval on x86_64 to reduce timing errors.
* Default to Win32 threads, not pthreads, if both are present.
* Various build-script fixes.
---
3.3
---
* Add ``include`` parameter to ``setuptools.find_packages()``.
---
3.2
---
* Pull Request #39: Add support for C++ targets from Cython ``.pyx`` files.
* Issue #162: Update dependency on certifi to 1.0.1.
* Issue #164: Update dependency on wincertstore to 0.2.
0.3.5:
While we've not added any additional functionality, we have fixed
many bugs from internal testing (clang static analysis and valgrind)
and also downstream distribution issues. We've also reduced the
memory thrashing dramatically. Going from 16,000 reallocations and
about 400MiB memory usage when playing a 2 minute midi down to
about 600 reallocations and only 8MiB memory usage!
What is new in this release:
Greatly reduced the heap usage (was a regression introduced in
0.2.3)
OpenAL support: Fixed audio output on big-endian systems. Fixed
audio skips at song start.
OSS support: No longer uses mmap mode for better compatibility.
This gains us NetBSD and OpenBSD support.
Worked around an invalid memory read found by valgrind when
playing Beethoven's Fur Elise.rmi at 44100 Hz using the old
MIDIA patch-set from 1994.
Build fixes for MSVC. Revised visibility attributes usage.
0.3.4:
This release marks the end of further development in the 0.3 branch.
We will do bug-fixes to help stabilize platforms, but no new
functionality will be added after this.
What is new in this release:
OpenAL support: This gains us OSX and other platforms that
OpenAL supports for sound output!
DOS DJGPP support: This goes a long way to helping other DOS
based applications like UHexen2.
MinGW support: This gains us win32 and win64 support using this
toolchain.
Fedora support: We are now ready to see this get pushed upstream
to Fedora.
New portable file and path-name system to handle cross-platform
support.
Support for Debian/kFreeBSD, Debian/Hurd and other Debian archs.
Many bug fixes, code clean-ups and cosmetic fixes.
0.3.3:
This is the first package to be officially uploaded to Debian.
default to hidden visibility and only export our API functions
windows lean and mean to help compile times on Windows
cli and xcode work now on OSX
better FreeBSD support
Supported platforms are Debian, FreeBSD, Windows and OSX (but only
for WAV output)
0.3.2:
Now with Microsoft Visual Studio support.
0.8.0 (2014-03-22):
- Adapt for the AST in Python 3.4.
- Fix caret position on SyntaxError.
- Fix crash on Python 2.x with some doctest SyntaxError.
- Add tox.ini.
- The `PYFLAKES_NODOCTEST` environment variable has been replaced with the
`PYFLAKES_DOCTEST` environment variable (with the opposite meaning).
Doctest checking is now disabled by default; set the environment variable
to enable it.
- Correctly parse incremental `__all__ += [...]`.
- Catch return with arguments inside a generator (Python <= 3.2).
- Do not complain about `_` in doctests.
- Drop deprecated methods `pushFunctionScope` and `pushClassScope`.
libFS is the protocol binding library used by clients of X Font Servers (xfs),
such as xfsinfo, fslsfonts, and the X servers themselves.
This minor maintenance release includes fixes for libxtrans 1.3 compatibility,
removal of dead code, and cleanups of issues found by static analyzers.
Adam Jackson (1):
Fix build with xtrans 1.3
Alan Coopersmith (14):
Fix typo in readme ("xfslsfonts" should be "fslsfonts")
Require ANSI C89 pre-processor, drop pre-C89 token pasting support
Fix a couple comment typos
Drop Cray (WORD64/MUSTCOPY) support
Add AC_USE_SYSTEM_EXTENSIONS to expose non-standard extensions
Reduce scope & remove unneeded assignment of defaultp in FSGetErrorText()
If EAGAIN == EWOULDBLOCK, only need to check errno for one of them
Remove unused internal helper _FSGetHostname
Remove unused internal helper _FSAllocScratch
Remove unused internal helper _FSEventsQueued
Remove unused internal helper _FSWireToEvent
Replace malloc(strlen + 1); strcpy() with strdup()
Use strlcpy instead of strcpy/strncpy if it is available
libFS 1.0.6
Jeremy Huddleston Sequoia (2):
Update error loop to correctly handle error in i==0 case
FSOpenServer: Fix double-free in error path
2.0.3:
- Source code now packaged in a .tar.bz2 instead of .tar.gz.
- Fixed "make docs" for out-of-tree builds.
- No longer builds annoying wxWidgets test program by default.
- Fixed logic bug in UTF-8 string processing.
- Fixed infinite loop on some .zip files with symlinks.
- Enabled CD-ROM support on Haiku OS.
- Fixed Win64 support.
- Fixed OpenBSD support.
- Fixed building of readline support in test program.
- Fixed .zip archiver losing files in some cases.
- Corrected copyright dates in license.
- Other minor tweaks and fixes.
2.0.1:
- Fixed building with gcc 4.4.
- Workaround bug with lzma archiver not being able to reopen the same
file twice.
- Fixed reading of /proc/self/exe on Linux when calculating base dir.
Fixes unexpected PHYSFS_init() failures.
- Fixed cross-compiling problems.
- Fixed building with GCC on several platforms that don't support the
-fvisibility=hidden option.
- Added support for building with the Mac OS X 10.6 SDK.
- Fixed latin1-to-utf8 encoding conversion issue.
- Fixed logic error in the OS/2 code.
- Replaced some C++-style comments with C-style equivalents.
- Fixed compiler warning on newer Linux systems.
- Added support for GNU/Hurd.
- Doxygen corrections.
- Setting $HOME to a missing directory on Unix will no longer cause
PHYSFS_init() to fail.
- Improved CD-ROM/DVD-ROM detection for Linux systems.
- Corrected file sharing permissions on Windows and PocketPC.
- Other minor fixes.
2.0:
PhysicsFS 2.0 offers many improvements over the 1.0 branch.
- New CMake-based build system. The autotools mess is gone, as are all
the specialized project files for various toolchains. We now maintain
one text file that describes the project, and use CMake
(http://www.cmake.org/) to generate real project files from there...it
produces standard Makefiles for most Unixes and BeOS, but also project
files for KDevelop, Xcode, Visual Studio 6/7/8, Watcom, Borland, and
other build tools on Windows and Mac OS X. If your platform or build
tool isn't supported, energy is better spent on enhancing CMake than
creating another project file for PhysicsFS. OS/2 still uses a batch
file to build for now, but everything else is either using CMake or will
be dropped.
- New archiver: lzma support (7zip archives), thanks to Dennis Schridde.
- Unicode support! All PhysicsFS APIs that deal with strings now expect
them to be UTF-8 encoded, and will convert behind the scenes as
appropriate, so eventually your UTF-8 encoded Japanese characters will
become 2-byte WCHAR strings when looking for filenames on a Windows NTFS
disc, etc. Windows will try to use the appropriate codepage on
Win95/98/ME, and use the actual Unicode entry points on NT/XP/Vista,
CFStrings on Mac OS X, etc. The platform layers in PhysicsFS for all
supported OSes are now Unicode clean, except OS/2 (to be considered).
There are new PhysicsFS APIs to provide conversion between some common
character encodings.
- Applications may now supply their own allocators for PhysicsFS to use
internally. If you don't want to supply one, PhysicsFS uses a reasonable
default for the platform (such as malloc() on Unix, or CoreFoundation
APIs on Mac OS X).
- New API: PHYSFS_mount(). This supercedes PHYSFS_addToSearchPath().
This lets you put your archives at specific points in the interpolated
file system. If you have an archive mounted to "/some/subdir" then it
treats it as if every file in that archive is under the /some/subdir
directory (so /path/x.txt will be accessible at
/some/subdir/path/x.txt). Developers can still use
PHYSFS_addToSearchPath() if source/binary compatibility with PhysicsFS
1.0.x is important, and even mix and match calls with PHYSFS_mount().
- New API: PHYSFS_isInit(), to determine if the library is ready for use
when you don't have access to the results of a previous PHYSFS_init() call.
- New API: PHYSFS_symbolicLinksPermitted(), to determine this state when
you don't control the calls to PHYSFS_permitSymbolicLinks().
- Symlinks are now supported on Windows Vista and later:
PHYSFS_isSymbolicLink() and PHYSFS_permitSymbolicLinks() work with the
native filesystem as expected in the new Windows version without losing
binary compatibility with older Windows releases.
- Public headers no longer use size_t, so they work without any system
headers pre-included.
- Internal mutexes are now recursive on all platforms, which means it's
now safe to call most PHYSFS_* functions from inside an enumeration
callback (including performing more enumerations from inside an
enumeration!)
- Added unarchiver program as an example application, which actually
does enumerations from inside enumerations. :)
- Added initial shot at a wxWidgets-based test program, to supersede
test_physfs.c ... still a work in progress.
- Mac OS classic support has been dropped. It could be readded if CMake
is enhanced to support CodeWarrior or MPW, and the code moves from
FSSpec to FSRef functions for Unicode support. Mac OS 8/9 support will
remain in the stable 1.0 branch, and Mac OS X is still, of course, fully
supported everywhere.
- Improvements to support Cygwin, Mingw32, and MSYS.
- Mac OS X now has its own Carbon-based code, split out from unix.c,
which helps with functionality like Unicode and recursive mutexes...the
bits in posix.c are still used on OS X, though.
- OS/2 now builds with Innotek GCC and klibc instead of EMX (although
can probably still work with EMX).
- Most systems can make do with PHYSFS_init(NULL) now (but still should
have argv[0] for cases where they can't!). This includes Linux and
systems that present a Linux-like /proc filesystem with /proc/self/exe ...
- Compiles on BeOS again (was broken in 1.1.0). Haiku is now a supported
target platform as well.
- On GCC 4 and later, will build with -fvisibility=hidden, so the only
symbols exported from the library are the public APIs. This makes the
library smaller and faster when built as a shared library, not to
mention prevents namespace pollution.
- Reduced malloc pressure a little more (see __PHYSFS_smallAlloc() in
physfs_internal.h). More to come.
- Other bug fixes, cleanups, refactoring, and improvements. A LOT of
internal code has changed...you can check the Mercurial repository
history for specific details.
---
3.7
---
* Gnome keyring no longer relies on the GNOME_KEYRING_CONTROL environment
variable.
* Issue #140: Restore compatibility for older versions of PyWin32.
---
3.6
---
* `Pull Request #1 (github) <https://github.com/jaraco/keyring/pull/1>`_:
Add support for packages that wish to bundle keyring by using relative
imports throughout.
---
3.5
---
* Issue #49: Give the backend priorities a 1.5 multiplier bump when an
XDG_CURRENT_DESKTOP environment variable matches the keyring's target
environment.
* Issue #99: Clarified documentation on location of config and data files.
Prepared the code base to treat the two differently on Unix-based systems.
For now, the behavior is unchanged.
---
3.4
---
* Extracted FileBacked and Encrypted base classes.
* Add a pyinstaller hook to expose backend modules. Ref #124
* Pull request #41: Use errno module instead of hardcoding error codes.
* SecretService backend: correctly handle cases when user dismissed
the collection creation or unlock prompt.
---
3.3
---
* Pull request #40: KWallet backend will now honor the ``KDE_FULL_SESSION``
environment variable as found on openSUSE.
-----
3.2.1
-----
* SecretService backend: use a different function to check that the
backend is functional. The default collection may not exist, but
the collection will remain usable in that case.
Also, make the error message more verbose.
Resolves https://bugs.launchpad.net/bugs/1242412.
---
3.2
---
* Issue #120: Invoke KeyringBackend.priority during load_keyring to ensure
that any keyring loaded is actually viable (or raises an informative
exception).
* File keyring:
- Issue #123: fix removing items.
- Correctly escape item name when removing.
- Use with statement when working with files.
* Add a test for removing one item in group.
* Issue #81: Added experimental support for third-party backends. See
`keyring.core._load_library_extensions` for information on supplying
a third-party backend.
---
3.1
---
* All code now runs natively on both Python 2 and Python 3, no 2to3 conversion
is required.
* Testsuite: clean up, and make more use of unittest2 methods.
-----
3.0.5
-----
* Issue #114: Fix logic in pyfs detection.
-----
3.0.4
-----
* Issue #114: Fix detection of pyfs under Mercurial Demand Import.
-----
3.0.3
-----
* Simplified the implementation of ``keyring.core.load_keyring``. It now uses
``__import__`` instead of loading modules explicitly. The ``keyring_path``
parameter to ``load_keyring`` is now deprecated. Callers should instead
ensure their module is available on ``sys.path`` before calling
``load_keyring``. Keyring still honors ``keyring-path``. This change fixes
Issue #113 in which the explicit module loading of keyring modules was
breaking package-relative imports.
-----
3.0.2
-----
* Renamed ``keyring.util.platform`` to ``keyring.util.platform_``. As reported
in Issue #112 and `mercurial_keyring #31
<https://bitbucket.org/Mekk/mercurial_keyring/issue/31>`_ and in `Mercurial
itself <http://bz.selenic.com/show_bug.cgi?id=4029>`_, Mercurial's Demand
Import does not honor ``absolute_import`` directives, so it's not possible
to have a module with the same name as another top-level module. A patch is
in place to fix this issue upstream, but to support older Mercurial
versions, this patch will remain for some time.
-----
3.0.1
-----
* Ensure that modules are actually imported even in Mercurial's Demand Import
environment.
---
3.0
---
* Removed support for Python 2.5.
* Removed names in ``keyring.backend`` moved in 1.1 and previously retained
for compatibilty.
-----
2.1.1
-----
* Restored Python 2.5 compatibility (lost in 2.0).
---
2.1
---
* Issue #10: Added a 'store' attribute to the OS X Keyring, enabling custom
instances of the KeyringBackend to use another store, such as the
'internet' store. For example::
keys = keyring.backends.OS_X.Keyring()
keys.store = 'internet'
keys.set_password(system, user, password)
keys.get_password(system, user)
The default for all instances can be set in the class::
keyring.backends.OS_X.Keyring.store = 'internet'
* GnomeKeyring: fix availability checks, and make sure the warning
message from pygobject is not printed.
* Fixes to GnomeKeyring and SecretService tests.
-----
2.0.3
-----
* Issue #112: Backend viability/priority checks now are more aggressive about
module presence checking, requesting ``__name__`` from imported modules to
force the demand importer to actually attempt the import.
-----
2.0.2
-----
* Issue #111: Windows backend isn't viable on non-Windows platforms.
-----
2.0.1
-----
* Issue #110: Fix issues with ``Windows.RegistryKeyring``.
---
2.0
---
* Issue #80: Prioritized backend support. The primary interface for Keyring
backend classes has been refactored to now emit a 'priority' based on the
current environment (operating system, libraries available, etc). These
priorities provide an indication of the applicability of that backend for
the current environment. Users are still welcome to specify a particular
backend in configuration, but the default behavior should now be to select
the most appropriate backend by default.
-----
1.6.1
-----
* Only include pytest-runner in 'setup requirements' when ptr invocation is
indicated in the command-line (Issue #105).
---
1.6
---
* GNOME Keyring backend:
- Use the same attributes (``username`` / ``service``) as the SecretService
backend uses, allow searching for old ones for compatibility.
- Also set ``application`` attribute.
- Correctly handle all types of errors, not only ``CANCELLED`` and ``NO_MATCH``.
- Avoid printing warnings to stderr when GnomeKeyring is not available.
* Secret Service backend:
- Use a better label for passwords, the same as GNOME Keyring backend uses.
---
1.5
---
* SecretService: allow deleting items created using previous python-keyring
versions.
Before the switch to secretstorage, python-keyring didn't set "application"
attribute. Now in addition to supporting searching for items without that
attribute, python-keyring also supports deleting them.
* Use ``secretstorage.get_default_collection`` if it's available.
On secretstorage 1.0 or later, python-keyring now tries to create the
default collection if it doesn't exist, instead of just raising the error.
* Improvements for tests, including fix for Issue #102.
---
1.4
---
* Switch GnomeKeyring backend to use native libgnome-keyring via
GObject Introspection, not the obsolete python-gnomekeyring module.
---
1.3
---
* Use the `SecretStorage library <https://pypi.python.org/pypi/SecretStorage>`_
to implement the Secret Service backend (instead of using dbus directly).
Now the keyring supports prompting for and deleting passwords. Fixes#69,
#77, and #93.
* Catch `gnomekeyring.IOError` per the issue `reported in Nova client
<https://bugs.launchpad.net/python-novaclient/+bug/1116302>`_.
* Issue #92 Added support for delete_password on Mac OS X Keychain.
-----
1.2.3
-----
* Fix for Encrypted File backend on Python 3.
* Issue #97 Improved support for PyPy.
-----
1.2.2
-----
* Fixed handling situations when user cancels kwallet dialog or denies access
for the app.
-----
1.2.1
-----
* Fix for kwallet delete.
* Fix for OS X backend on Python 3.
* Issue #84: Fix for Google backend on Python 3 (use of raw_input not caught
by 2to3).
---
1.2
---
* Implemented delete_password on most keyrings. Keyring 2.0 will require
delete_password to implement a Keyring. Fixes#79.
-----
1.1.2
-----
* Issue #78: pyfilesystem backend now works on Windows.
-----
1.1.1
-----
* Fixed MANIFEST.in so .rst files are included.
---
1.1
---
This is the last build that will support installation in a pure-distutils
mode. Subsequent releases will require setuptools/distribute to install.
Python 3 installs have always had this requirement (for 2to3 install support),
but starting with the next minor release (1.2+), setuptools will be required.
Additionally, this release has made some substantial refactoring in an
attempt to modularize the backends. An attempt has been made to maintain 100%
backward-compatibility, although if your library does anything fancy with
module structure or clasess, some tweaking may be necessary. The
backward-compatible references will be removed in 2.0, so the 1.1+ releases
represent a transitional implementation which should work with both legacy
and updated module structure.
* Added a console-script 'keyring' invoking the command-line interface.
* Deprecated _ExtensionKeyring.
* Moved PasswordSetError and InitError to an `errors` module (references kept
for backward-compatibility).
* Moved concrete backend implementations into their own modules (references
kept for backward compatibility):
- OSXKeychain -> backends.OS_X.Keyring
- GnomeKeyring -> backends.Gnome.Keyring
- SecretServiceKeyring -> backends.SecretService.Keyring
- KDEKWallet -> backends.kwallet.Keyring
- BasicFileKeyring -> backends.file.BaseKeyring
- CryptedFileKeyring -> backends.file.EncryptedKeyring
- UncryptedFileKeyring -> backends.file.PlaintextKeyring
- Win32CryptoKeyring -> backends.Windows.EncryptedKeyring
- WinVaultKeyring -> backends.Windows.WinVaultKeyring
- Win32CryptoRegistry -> backends.Windows.RegistryKeyring
- select_windows_backend -> backends.Windows.select_windows_backend
- GoogleDocsKeyring -> backends.Google.DocsKeyring
- Credential -> keyring.credentials.Credential
- BaseCredential -> keyring.credentials.SimpleCredential
- EnvironCredential -> keyring.credentials.EnvironCredential
- GoogleEnvironCredential -> backends.Google.EnvironCredential
- BaseKeyczarCrypter -> backends.keyczar.BaseCrypter
- KeyczarCrypter -> backends.keyczar.Crypter
- EnvironKeyczarCrypter -> backends.keyczar.EnvironCrypter
- EnvironGoogleDocsKeyring -> backends.Google.KeyczarDocsKeyring
- BasicPyfilesystemKeyring -> backends.pyfs.BasicKeyring
- UnencryptedPyfilesystemKeyring -> backends.pyfs.PlaintextKeyring
- EncryptedPyfilesystemKeyring -> backends.pyfs.EncryptedKeyring
- EnvironEncryptedPyfilesystemKeyring -> backends.pyfs.KeyczarKeyring
- MultipartKeyringWrapper -> backends.multi.MultipartKeyringWrapper
* Officially require Python 2.5 or greater (although unofficially, this
requirement has been in place since 0.10).
---
1.0
---
This backward-incompatible release attempts to remove some cruft from the
codebase that's accumulated over the versions.
* Removed legacy file relocation support. `keyring` no longer supports loading
configuration or file-based backends from ~. If upgrading from 0.8 or later,
the files should already have been migrated to their new proper locations.
If upgrading from 0.7.x or earlier, the files will have to be migrated
manually.
* Removed CryptedFileKeyring migration support. To maintain an existing
CryptedFileKeyring, one must first upgrade to 0.9.2 or later and access the
keyring before upgrading to 1.0 to retain the existing keyring.
* File System backends now create files without group and world permissions.
Fixes#67.
------
0.10.1
------
* Merged 0.9.3 to include fix for #75.
----
0.10
----
* Add support for using `Keyczar <http://www.keyczar.org/>`_ to encrypt
keyrings. Keyczar is "an open source cryptographic toolkit designed to make
it easier and safer for developers to use cryptography in their
applications."
* Added support for storing keyrings on Google Docs or any other filesystem
supported by pyfilesystem.
* Fixed issue in Gnome Keyring when unicode is passed as the service name,
username, or password.
* Tweaked SecretService code to pass unicode to DBus, as unicode is the
preferred format.
* Issue #71 - Fixed logic in CryptedFileKeyring.
* Unencrypted keyring file will be saved with user read/write (and not group
or world read/write).
-----
0.9.3
-----
* Ensure migration is run when get_password is called. Fixes#75. Thanks to
Marc Deslauriers for reporting the bug and supplying the patch.
-----
0.9.2
-----
* Keyring 0.9.1 introduced a whole different storage format for the
CryptedFileKeyring, but this introduced some potential compatibility issues.
This release incorporates the security updates but reverts to the INI file
format for storage, only encrypting the passwords and leaving the service
and usernames in plaintext. Subsequent releases may incorporate a new
keyring to implement a whole-file encrypted version. Fixes#64.
* The CryptedFileKeyring now requires simplejson for Python 2.5 clients.
-----
0.9.1
-----
* Fix for issue where SecretServiceBackend.set_password would raise a
UnicodeError on Python 3 or when a unicode password was provided on Python
2.
* CryptedFileKeyring now uses PBKDF2 to derive the key from the user's
password and a random hash. The IV is chosen randomly as well. All the
stored passwords are encrypted at once. Any keyrings using the old format
will be automatically converted to the new format (but will no longer be
compatible with 0.9 and earlier). The user's password is no longer limited
to 32 characters. PyCrypto 2.5 or greater is now required for this keyring.
---
0.9
---
* Add support for GTK 3 and secret service D-Bus. Fixes#52.
* Issue #60 - Use correct method for decoding.
-----
0.8.1
-----
* Fix regression in keyring lib on Windows XP where the LOCALAPPDATA
environment variable is not present.
---
0.8
---
* Mac OS X keyring backend now uses subprocess calls to the `security`
command instead of calling the API, which with the latest updates, no
longer allows Python to invoke from a virtualenv. Fixes issue #13.
* When using file-based storage, the keyring files are no longer stored
in the user's home directory, but are instead stored in platform-friendly
locations (`%localappdata%\Python Keyring` on Windows and according to
the freedesktop.org Base Dir Specification
(`$XDG_DATA_HOME/python_keyring` or `$HOME/.local/share/python_keyring`)
on other operating systems). This fixes#21.
*Backward Compatibility Notice*
Due to the new storage location for file-based keyrings, keyring 0.8
supports backward compatibility by automatically moving the password
files to the updated location. In general, users can upgrade to 0.8 and
continue to operate normally. Any applications that customize the storage
location or make assumptions about the storage location will need to take
this change into consideration. Additionally, after upgrading to 0.8,
it is not possible to downgrade to 0.7 without manually moving
configuration files. In 1.0, the backward compatibilty
will be removed.
-----
0.7.1
-----
* Removed non-ASCII characters from README and CHANGES docs (required by
distutils if we're to include them in the long_description). Fixes#55.
---
0.7
---
* Python 3 is now supported. All tests now pass under Python 3.2 on
Windows and Linux (although Linux backend support is limited). Fixes#28.
* Extension modules on Mac and Windows replaced by pure-Python ctypes
implementations. Thanks to Jerome Laheurte.
* WinVaultKeyring now supports multiple passwords for the same service. Fixes
#47.
* Most of the tests don't require user interaction anymore.
* Entries stored in Gnome Keyring appears now with a meaningful name if you try
to browser your keyring (for ex. with Seahorse)
* Tests from Gnome Keyring no longer pollute the user own keyring.
* `keyring.util.escape` now accepts only unicode strings. Don't try to encode
strings passed to it.
-----
0.6.2
-----
* fix compiling on OSX with XCode 4.0
-----
0.6.1
-----
* Gnome keyring should not be used if there is no DISPLAY or if the dbus is
not around (https://bugs.launchpad.net/launchpadlib/+bug/752282).
---
0.6
---
* Added `keyring.http` for facilitating HTTP Auth using keyring.
* Add a utility to access the keyring from the command line.
version 3.12.0
gnome-autogen.sh: Fix check if stdin is a tty
Commit 7f977b021462 introduced a check if stdin is ins't a tty, and
prevent printing terminal codes in this case. But the check was wrong
and always failed.
https://bugzilla.gnome.org/show_bug.cgi?id=726892
gnome-autogen: require automake 1.11.2
This is the version of automake that introduced ACLOCAL_PATH support, so
make sure that we have it before attempting to configure the package.
gnome-common: use ACLOCAL_PATH over ACLOCAL_FLAGS
jhbuild has set this variable for more than two years.
https://bugzilla.gnome.org/show_bug.cgi?id=726208
gnome-autogen.sh: correct IFS value
Due to a likely copy-paste mistake, the default value of IFS was being
set to 9 spaces instead of a tab and a space. Fix that.
https://bugzilla.gnome.org/show_bug.cgi?id=726208
gnome-autogen.sh: Check for appdata-xml.m4 with APPDATA_XML
compiler-flags: Simplify a case statement slightly
compiler-flags: Replace deprecated AC_HELP_STRING with AS_HELP_STRING
Read the dirlist file unconditionally
Pretend is a library to make stubbing with Python easier.
What is stubbing?
Stubbing is a technique for writing tests. You may hear the term
mixed up with mocks, fakes, or doubles. Basically a stub is an
object that returns pre-canned responses, rather than doing any
computation.
The docbook2mdoc utility is a converter from DocBook into mdoc.
Unlike most DocBook utilities, it's a standalone ISC-licensed ISO
C utility that should compile on any modern UNIX system.
The pod2mdoc utility is a converter from POD into mdoc. It's meant
to operate like pod2man; however, it doesn't require a Perl
installation: pod2mdoc is a standalone ISC-licensed ISO C utility
and should compile on any modern UNIX system.
