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

Request to future self and prospective users #11

Closed
klauer opened this issue Feb 3, 2021 · 2 comments
Closed

Request to future self and prospective users #11

klauer opened this issue Feb 3, 2021 · 2 comments

Comments

@klauer
Copy link
Contributor

klauer commented Feb 3, 2021

Expected Behavior

Do not base things on current client/server code until a large refactor goes through.

  • The API is a mess, as to be expected for a rushed, incomplete evening side project.
  • Client API should be restructured to nicely separate protocol/asyncio implementation
  • The end goal should be a user-friendly, extensible client and server API

Current Behavior

You will probably ignore this and continue with what's here.

Possible Solution

Listen to this issue

@klauer
Copy link
Contributor Author

klauer commented Feb 8, 2021

Adding to the todo list:

  • Need to look into resource cleanup and tracking on the protocol level

@klauer
Copy link
Contributor Author

klauer commented Nov 10, 2023

Obvious issue; closing:

  • "Use at your own risk"
  • "Use pyads + adstool"

@klauer klauer closed this as completed Nov 10, 2023
@klauer klauer closed this as not planned Won't fix, can't repro, duplicate, stale Nov 10, 2023
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

No branches or pull requests

1 participant