| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Haven't upgraded but I know that the binary/non-binary problem has gotten me before, especially when trying to explain to others what they have to do to not get errors when installing stuff. So just having everyone decide what they want as suggested here is probably better. |
Sorry, something went wrong.
|
Just to be clear, this broke build for everyone who uses databases[postgresql] and psycopg2-binary, right? I'm surprised there isn't more voting/commenting on this thread, and no back-refs from other projects to this issue. For anyone playing along at home, "databases[postgresql]<0.4.0", should temporarily fix your build errors. Thanks for all the hard work, btw :) |
Sorry, something went wrong.
|
Version pinning ftw, yes. There is another option: databases==0.4.0 asyncpg==0.21.0 |
Sorry, something went wrong.
|
Yes, this broke my builds too. I think the option given by Tom: #204 (comment) is very reasonable. Thanks for the fast response and the work done on this! |
Sorry, something went wrong.
|
@encode/maintainers can please somebody approve this deal breaking fix. |
Sorry, something went wrong.
|
I'm having this issue too, please consider this PR. |
Sorry, something went wrong.
There was a problem hiding this comment.
Sounds good — let's consider a 0.5.0 bump perhaps. (Or, alternatively, let's skip bumping versions in this PR, and issue a proper release PR later when we're ready to issue 0.5.0.)
Sorry, something went wrong.
| ## 0.4.1 (October 21st, 2020) | ||
|
|
||
| ### Fixed | ||
|
|
||
| * Remove package dependency on the synchronous DB drivers (#256) | ||
|
|
There was a problem hiding this comment.
Are we okay with bumping to 0.5.0? I think this qualifies as an entry for a "Changed" section, rather than "Fixed". That way people that are currently pinned to 0.4.* will be fine.
I'm not sure I understood the broken build issue with these direct dependencies, though (edit: I assume that's related to 3.9 and the lack of wheels?) but I think sticking closer to SemVer is a good idea here?
Sorry, something went wrong.
There was a problem hiding this comment.
We have literally no other features to release rather than the broken package installation of 0.4.0 😂 And it was planned for 0.4.0 long before I became a maintainer, so I honestly just overlooked this PR.
Sorry, something went wrong.
There was a problem hiding this comment.
Besides, we have to bump the version, otherwise it does not deploy to pypi and many people continue suffering.
Thanks for the approval, I will carry on with the release now.
Sorry, something went wrong.
There was a problem hiding this comment.
Makes sense!
Sorry, something went wrong.
Sorry, something went wrong.
|
|
||
| The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/). | ||
|
|
||
| ## 0.4.1 (October 21st, 2020) |
There was a problem hiding this comment.
Btw, the release date is a bit out of sync now. :-)
Should be:
## 0.4.1 (November 16th, 2020)
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Related to #204
This should fix my own builds and I guess other people's too.