A platform-independent file lock for Python.
active 2023-08-16 → 2023-08-18 (UTC)
Complete coverage26,405 / 26,405 hourly files (100%) · 2 absent upstream2023-08-15 → 2026-08-19 (UTC)
Events
11
Pushes
0
Pull requests
1
Issues
3
Stars
1
Forks
1
Activity over time
Daily event counts in the loaded window
Line chart, 3 days from 2023-08-16 to 2023-08-18. Pushes: 0 total, peak 0 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 3 total, peak 2 in a day. Comments: 5 total, peak 4 in a day. Stars: 1 total, peak 1 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| gaborbernat | 5 | 0 | 0 | 3 |
| fostiropoulos | 3 | 0 | 1 | 1 |
| asqui | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#258gaborbernat2023-08-18 14:40The type annotation for the `lock_file` `__init__` parameter is too narrow
- Issue comment#234gaborbernat2023-08-18 14:39sdist is missing tox.ini
- Issue comment#233gaborbernat2023-08-18 14:393.12.0: test_bad_lock_file[current_directory-UnixFileLock] fails
- Issue#233gaborbernat2023-08-18 14:393.12.0: test_bad_lock_file[current_directory-UnixFileLock] fails
- Issue#261gaborbernat2023-08-18 14:37Why can I acquire the same lock twice?
- Issue comment#261asqui2023-08-18 11:01Why can I acquire the same lock twice?
- Issue comment#261fostiropoulos2023-08-17 20:38Why can I acquire the same lock twice?
- Issue#261fostiropoulos2023-08-17 20:36Why can I acquire the same lock twice?
- Pull request#260fostiropoulos2023-08-16 20:52
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.