You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While working on (3.) in #20, I am running into the problem of there being no associated dynamic version with the fastpair==0.1.0 tag, which is causing the pip install -e . to fail.
The two options (IMHO) are a conservative approach [1,2] or a more aggressive approach [2] that does it all at once.
conservative approach (2 PRs):
explicitly declaring version = "v0.1.0" in pyproject.toml in a first PR addressing (3.)
(perhaps create a v0.1.1 tag and associated release, but this might be overkill)
proceed to step 2
one stroke (1 PR):
delete the fastpair==0.1.0 tag (remote & local)
declare dynamic = ["version"] in pyproject.toml
@carsonfarmer Let me know if (A) you have any questions/concerns here; and (B) which approach you'd like me to take.
The text was updated successfully, but these errors were encountered:
Since we didn't have tags and releases before, I don't see any reason not to just go with option 2. But I'm happy to adopt either, I leave it up to you.
While working on (3.) in #20, I am running into the problem of there being no associated dynamic version with the
fastpair==0.1.0
tag, which is causing thepip install -e .
to fail.The two options (IMHO) are a conservative approach [1,2] or a more aggressive approach [2] that does it all at once.
version = "v0.1.0"
inpyproject.toml
in a first PR addressing (3.)v0.1.1
tag and associated release, but this might be overkill)fastpair==0.1.0
tag (remote & local)dynamic = ["version"]
inpyproject.toml
@carsonfarmer Let me know if (A) you have any questions/concerns here; and (B) which approach you'd like me to take.
The text was updated successfully, but these errors were encountered: