-
Notifications
You must be signed in to change notification settings - Fork 20
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update the README with information about how to access the correct development repository and get set up to contribute patches. Addresses the redirect request in issue #11 Change-Id: I642334318e42f11d00c258755d8fcbd5aabd8dac
- Loading branch information
Showing
23 changed files
with
19 additions
and
2,447 deletions.
There are no files selected for viewing
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,27 +1,27 @@ | ||
The lockfile package exports a LockFile class which provides a simple API for | ||
locking files. Unlike the Windows msvcrt.locking function, the fcntl.lockf | ||
and flock functions, and the deprecated posixfile module, the API is | ||
identical across both Unix (including Linux and Mac) and Windows platforms. | ||
The lock mechanism relies on the atomic nature of the link (on Unix) and | ||
mkdir (on Windows) system calls. An implementation based on SQLite is also | ||
provided, more as a demonstration of the possibilities it provides than as | ||
production-quality code. | ||
============================== | ||
Contributing to pylockfile | ||
============================== | ||
|
||
Note: In version 0.9 the API changed in two significant ways: | ||
The pylockfile library has been adopted by the OpenStack Oslo program, | ||
and development is now managed using our regular tool chain. | ||
|
||
* It changed from a module defining several classes to a package containing | ||
several modules, each defining a single class. | ||
If you would like to contribute to the development of OpenStack, | ||
you must follow the steps in the "If you're a developer, start here" | ||
section of this page: | ||
|
||
* Where classes had been named SomethingFileLock before the last two words | ||
have been reversed, so that class is now SomethingLockFile. | ||
http://wiki.openstack.org/HowToContribute | ||
|
||
The previous module-level definitions of LinkFileLock, MkdirFileLock and | ||
SQLiteFileLock will be retained until the 1.0 release. | ||
Once those steps have been completed, changes to OpenStack | ||
should be submitted for review via the Gerrit tool, following | ||
the workflow documented at: | ||
|
||
Available on GitHub from: | ||
http://wiki.openstack.org/GerritWorkflow | ||
|
||
git://github.com/smontanaro/pylockfile.git | ||
If you would like to fork or clone the repository from GitHub, please | ||
use https://github.com/openstack/pylockfile instead of this | ||
repository. However, pull requests submitted through GitHub will be | ||
ignored. | ||
|
||
To install: | ||
Bugs should be filed on Launchpad, not GitHub: | ||
|
||
python setup.py install | ||
https://bugs.launchpad.net/pylockfile |
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.