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
{{ message }}
Repository navigation
Relax top end of Python version range specifier? #161
to not put a cap on the highest supported version? This is singlehandedly requiring all of the repos in my product to specify the same < rules as fluent-logger-python even though we control our Python version and generally support the latest release.
Does fluent-logger-python do anything sufficiently weird that you would expect it to break on minor language versions? #148 suggests "not really", and I would prefer to not block our language upgrades on fluent-logger-python when the duck types are likely to just work!
The version pin tries to indicate that there is no data on it being tested or even minimally functioning. But I suppose you're right, caveat emptor and all that. I'll relax the restriction.
Activity
arcivanov commentedon Mar 10, 2020
The version pin tries to indicate that there is no data on it being tested or even minimally functioning. But I suppose you're right, caveat emptor and all that. I'll relax the restriction.
seansfkelley commentedon Mar 10, 2020
Yeah, I figured that was the reason, but I'm all for caveat emptor when it comes to Python.
Glad to hear it, and thanks for the quick response!
Release v0.9.6
Release v0.9.6
Release v0.9.6
Release v0.9.6
Release v0.9.6
Release v0.9.6