This repo is not properly retired. Retired repos can only have two files:
- README.rst
- gitreview
To cleanup the retirement of this repo, keeping these two files only and
removing the other remaining files if there is any.
Detail: https://etherpad.opendev.org/p/tc-retirement-cleanup
Change-Id: I83df72500e3646d9a8edbb663246817759168d07
Oslo libraries (especially those prefixed with oslo) are
really better suited for usage inside openstack, while libraries
from oslo without that prefix are better suited for all around
general usage so to avoid confusion take off the recommendation
to replace pylockfile with oslo.concurrency and just leave the better
matched fasteners as its replacement.
Also fixes a very tiny flake8 warning that was stopping the
pep8/flake8 job from working.
Change-Id: I1ec1cbfb4c7e371ed93627cffa2b32dbe0401069
Python 3.2/3.3 support would be dropped by
Infra team from mitaka,CI would no longer be testing it,
so projects should drop it also.
Change-Id: I3bdf7d052f744198e983ddedd6b5a41f24442925
* reorder sections
* add missing links on fasteners, oslo.concurrency and openstack-dev
* use ".. warning::" warning for the deprecation
* use reStructured Text syntax for the Documentation, Source and Bugs
links
* use ``code markup`` for code
* Replace installation command "python setup.py install" with
"pip install lockfile": pip is now prefered in 2015 and the command
gives the PyPI name of the project (which is not obvious, I would
expect "pylockfile", not "lockfile")
* fix other reStructured Text syntax errors
Change-Id: I386b9aa31b3c79589fe4d93f722aeccb3a8577ef
We have decided to remove Python 2.6 support, this commit
removes Python 2.6 classifier before dropping any Python
2.6 support in code.
Change-Id: I7f655bcfb59ab7b32274e403837c88956a8a7e1b
* Remove unused imports
* Add empty lines to respect the PEP8
* Sort imports
* Replace "timeout/10" with "timeout / 10" (add spaces)
* Fix style of comments
* Remove trailing spaces
* test_lockfile.py: add "# noqa" on the sqlite3 import, the import is
used to decide if we skip the test or not
* tox.ini: enable all warnings except F841 (which will be fixed
later)
Change-Id: I8218785f5cea23532357ec1756a3ab2255880d74
end_time takes timeout into account, so when time.time()
does hit the end_time, we should check if timeout was
set or not and throw either LockTimeout or AlreadyLocked.
Closes-Bug: #1472101
Change-Id: I1f369628e765a173ff0cafd01c31eca725b41cae
Docs indicates that lock.acquire(timeout=0) would not block, but it
does (for linklockfile) because 0 is not truthy, and the line:
timeout = timeout is not None and timeout or self.timeout
when timeout is 0 causes it to default to self.timeout, which by default is None.
So rewrite the condition better to take into account that timeout may
be set to 0.
Closes-Bug: #1468124
Closes-Bug: #1419127
Change-Id: Idf0d00977e79661e1eafd695d6e148e5f27e1840
The release notes script Oslo uses depends on being able to find
information in the README.rst file using a regex, so update the contents
of the file to match that pattern.
Change-Id: Idef33f0438263f7ca4d596b66a36bbe260b53dd4
To enable the addition of a new lockfile impl that
has some of the similar functionality as the existing impls
in pylockfile we need to break out what will be shared and
what will not be shared by the existing impls and the soon
to be added new impl.
Change-Id: I3fddfb05b78657ebed1449f0389004061e7e7082
Currently pbr is breaking markup safe usage in docs, the
not so obvious way to fix this is to place pbr in the
explicit requirements for pylockfile.
Closes-Bug: #1384919
Change-Id: I0bba2f28956aeeb70b1e15f82d6bb67fdbd49118
The global requirements repo has blocked 1.3b1, so
in order for pylockfile builds to stop failing so
should we. In the future we should investigate why
the requirements aren't syncing for this repo.
Change-Id: I8a999cc044d3687cc410b56b1db490e38b9b9a50
Ghanshyam Mann