-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bitbucket OAuth. Resolve #201. #280
Bitbucket OAuth. Resolve #201. #280
Conversation
6d88bae
to
84ca895
Compare
return None | ||
|
||
|
||
def set(key, value): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a lockfile
around this? The w+
flag gives me the race-condition heebie-jeebies.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, good catch.
The oauth bits look fine to me. Can you look at the lockfile question above and rebase on |
1c09721
to
43a827c
Compare
I still gotta look at the lockfile issue. FYI, I tested out using |
FYI, I did add a lockfile. |
Oh, I'd missed it. 👍 here. Feel free to merge. 🍡 |
- Implement OAuth2. Thanks to @ibuchanan for helping me navigate bitbucket's idiosyncratic implementation. - Add a bugwarrior.data file to the ~/.task directory, per [taskwarrior's third-party guidelines](https://taskwarrior.org/docs/3rd-party.html#guidelines).
- Use lockfile for writes. - Use 'r+' rather than 'rw'. (The latter raises an exception in python 3). - Catch ValueError if data file isn't JSON. - Add `get_data_path` helper function.
58f0414
to
e2dfc82
Compare
Bitbucket OAuth. Resolve #201.
bitbucket's idiosyncratic implementation.
third-party guidelines.