Evan Rusackas
Evan Rusackas
@dankor if you can do that rebase to remove conflicts, I think we can get this one merged more expediently now. Thanks in advance!
We're working toward 5.0, and I think that's the safe time to get this merged (finally). I've put it on the kanban board, just FYI :) Thanks for the contributions!
/korbit-review
Closing and reopening to get CI to spin again. @sebastianliebscher can you please add an entry to UPDATING.md to help folks who are upgrading mitigate any risks here?
Well, you know the "we don't support 2.x" party line I'm using ;) Is this still a thing in 3.x?
I assume this one is still happening in 4.x, but it's getting a little stale. Seems not many people are running into this.
I'm assuming this is still happening in 4.1.2? This has gone silent for a long time, and is a bit at-risk of being closed as inactive, but it sounds like...
It _looks like_ we're on `requests` 2.30.0 as of [this PR](https://github.com/apache/superset/pull/23986), but were already on 2.26.0 before that. However... `chardet` 5.1.0 seems to still exist in `integration.txt` (via `tox`) and...
Looks like we're on `requests` 2.31.0 since quite some time ago. The `chardet` situation has not changed. Assigning this to @john-bodley and @mistercrunch who might have solid opinions on versioning/licensing...
Hey folks... we're coming up on 6 months from the last comment. `chardet==5.1.0` is still in the `development.txt` file, but no longer in the `integration.txt` file. Better, but not perfect.