Skip to content
This repository has been archived by the owner on Nov 8, 2023. It is now read-only.

Exposing fileio is misleading #1

Closed
marcsello opened this issue Mar 11, 2020 · 1 comment
Closed

Exposing fileio is misleading #1

marcsello opened this issue Mar 11, 2020 · 1 comment

Comments

@marcsello
Copy link
Owner

  • bettersocket version: 0.1.0
  • Python version: 3
  • Operating System: Linux

Using fileio to check if anything is available to read is misleading, because it only reflect the state of the socket, not the internal buffer. Because of this, messages in the internal buffer may go unnoticed.

@marcsello
Copy link
Owner Author

As with the latest release, I've decided to remove the fileio function for the time being.
But I'm planning on making something similar in the next release, as this would be an useful function.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant