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

Update to responder 3.0.0.dev0, and support Python 3.13 #28

Merged
merged 3 commits into from
Jan 19, 2025

Conversation

amotl
Copy link
Member

@amotl amotl commented May 10, 2024

Responder has been refurbished and will work on Python 3.8 - 3.13 now.

@codecov-commenter
Copy link

codecov-commenter commented May 10, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.56%. Comparing base (28c01d4) to head (d39734d).
Report is 3 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff             @@
##             main      #28       +/-   ##
===========================================
+ Coverage   69.12%   82.56%   +13.44%     
===========================================
  Files          12       12               
  Lines         217      218        +1     
===========================================
+ Hits          150      180       +30     
+ Misses         67       38       -29     
Flag Coverage Δ
unittests 82.56% <100.00%> (+13.44%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@amotl
Copy link
Member Author

amotl commented Oct 23, 2024

Coming from kennethreitz/responder#522, we discovered a potential successor project to Responder: Dyne is a fork of Responder with batteries included, self-documenting OpenAPI endpoints, focused on extensibility, simplicity, usability, and elegance.

@amotl amotl changed the title Fix dependencies, using vanilla responder package from PyPI, version 2 Update to responder 3.0.0 Jan 19, 2025
@amotl amotl force-pushed the responder-vanilla branch from 02e40d3 to 9dee011 Compare January 19, 2025 01:56
@amotl
Copy link
Member Author

amotl commented Jan 19, 2025

We spent a few cycles of maintenance on the responder package, so it can be used by vasuki again.

/cc @kennethreitz

@amotl amotl force-pushed the responder-vanilla branch 3 times, most recently from 7ad1ca6 to 44f01f3 Compare January 19, 2025 04:26
@amotl amotl changed the title Update to responder 3.0.0 Update to responder 3.0.0, and support Python 3.13 Jan 19, 2025
@amotl amotl marked this pull request as ready for review January 19, 2025 04:27
@amotl amotl force-pushed the responder-vanilla branch from 44f01f3 to d39734d Compare January 19, 2025 04:28
@amotl amotl changed the title Update to responder 3.0.0, and support Python 3.13 Update to responder 3.0.0.dev0, and support Python 3.13 Jan 19, 2025
@amotl amotl merged commit 1031850 into main Jan 19, 2025
4 checks passed
@amotl amotl deleted the responder-vanilla branch January 19, 2025 04:29
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.

2 participants