Skip to content
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

dropped dependency on requests[chardet] #4467

Closed
wants to merge 4 commits into from

Conversation

sanderr
Copy link
Contributor

@sanderr sanderr commented Jun 28, 2022

Description

With the context given in psf/requests#6177 (comment), I think it should be safe to drop this requirement again. Do you agree?

Self Check:

Strike through any lines that are not applicable (~~line~~) then check the box

  • Attached issue to pull request
  • Changelog entry
  • Type annotations are present
  • Code is clear and sufficiently documented
  • No (preventable) type errors (check using make mypy or make mypy-diff)
  • Sufficient test cases (reproduces the bug/tests the requested feature)
  • Correct, in line with design
  • End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

  • Sufficient test cases (reproduces the bug/tests the requested feature)
  • Code is clear and sufficiently documented
  • Correct, in line with design

Copy link
Contributor

@Hugo-Inmanta Hugo-Inmanta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good until next chardet major bump !

Copy link
Contributor

@arnaudsjs arnaudsjs left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The merge of this PR will need to wait until requests==2.28.1 has been released.

Copy link
Contributor Author

@sanderr sanderr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't approve it either, but it looks good to me!

tests/test_app.py Outdated Show resolved Hide resolved
@Hugo-Inmanta Hugo-Inmanta added the merge-tool-ready This ticket is ready to be merged in label Jun 28, 2022
@inmantaci
Copy link
Contributor

Processing this pull request

inmantaci pushed a commit that referenced this pull request Jun 28, 2022
…n restored (PR #4467)

# Description

With the context given in psf/requests#6177 (comment), I think it should be safe to drop this requirement again. Do you agree?

# Self Check:

Strike through any lines that are not applicable (`~~line~~`) then check the box

- [ ] Attached issue to pull request
- [ ] Changelog entry
- [ ] Type annotations are present
- [ ] Code is clear and sufficiently documented
- [ ] No (preventable) type errors (check using make mypy or make mypy-diff)
- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

# Reviewer Checklist:

- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Code is clear and sufficiently documented
- [ ] Correct, in line with design
@inmantaci inmantaci removed the merge-tool-ready This ticket is ready to be merged in label Jun 28, 2022
@inmantaci
Copy link
Contributor

Failed to merge changes into iso4 due to merge conflict.Please open a pull request for these branches separately.

@inmantaci
Copy link
Contributor

Merged into branches master in e34829f

inmantaci pushed a commit that referenced this pull request Jun 28, 2022
…n restored (PR #4467)

# Description

With the context given in psf/requests#6177 (comment), I think it should be safe to drop this requirement again. Do you agree?

# Self Check:

Strike through any lines that are not applicable (`~~line~~`) then check the box

- [ ] Attached issue to pull request
- [ ] Changelog entry
- [ ] Type annotations are present
- [ ] Code is clear and sufficiently documented
- [ ] No (preventable) type errors (check using make mypy or make mypy-diff)
- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

# Reviewer Checklist:

- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Code is clear and sufficiently documented
- [ ] Correct, in line with design
@inmantaci
Copy link
Contributor

Not closing this pull request due to previously commented issues for some of the destination branches. Please open a separate pull request for those branches. You can safely close this pull request and delete the source branch.

@inmantaci
Copy link
Contributor

This branch was not deleted as it seems to still be in use.

@inmantaci
Copy link
Contributor

Processing #4472.

inmantaci pushed a commit that referenced this pull request Jun 28, 2022
…n restored (PR #4467)

Pull request opened by the merge tool on behalf of #4467
@sanderr
Copy link
Contributor Author

sanderr commented Jul 5, 2022

Merged in iso4 in 03997ce

@sanderr sanderr closed this Jul 5, 2022
@sanderr sanderr deleted the drop-chardet-constraint branch July 5, 2022 07:44
arnaudsjs pushed a commit that referenced this pull request Jul 28, 2022
…n restored (PR #4467)

With the context given in psf/requests#6177 (comment), I think it should be safe to drop this requirement again. Do you agree?

Strike through any lines that are not applicable (`~~line~~`) then check the box

- [ ] Attached issue to pull request
- [ ] Changelog entry
- [ ] Type annotations are present
- [ ] Code is clear and sufficiently documented
- [ ] No (preventable) type errors (check using make mypy or make mypy-diff)
- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Code is clear and sufficiently documented
- [ ] Correct, in line with design
arnaudsjs pushed a commit that referenced this pull request Jul 28, 2022
…n restored (PR #4467)

With the context given in psf/requests#6177 (comment), I think it should be safe to drop this requirement again. Do you agree?

Strike through any lines that are not applicable (`~~line~~`) then check the box

- [ ] Attached issue to pull request
- [ ] Changelog entry
- [ ] Type annotations are present
- [ ] Code is clear and sufficiently documented
- [ ] No (preventable) type errors (check using make mypy or make mypy-diff)
- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Code is clear and sufficiently documented
- [ ] Correct, in line with design
arnaudsjs pushed a commit that referenced this pull request Jul 28, 2022
…n restored (PR #4467)

With the context given in psf/requests#6177 (comment), I think it should be safe to drop this requirement again. Do you agree?

Strike through any lines that are not applicable (`~~line~~`) then check the box

- [ ] Attached issue to pull request
- [ ] Changelog entry
- [ ] Type annotations are present
- [ ] Code is clear and sufficiently documented
- [ ] No (preventable) type errors (check using make mypy or make mypy-diff)
- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Correct, in line with design
- [ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

- [ ] Sufficient test cases (reproduces the bug/tests the requested feature)
- [ ] Code is clear and sufficiently documented
- [ ] Correct, in line with design
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants