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.

Sign up for GitHub

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

Core: update requirements #2716

Merged
merged 3 commits into from
Feb 19, 2024
Merged

Core: update requirements #2716

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0161ef7
requirements: update modules
Berserker66 Jan 13, 2024
57ebf82
Update requirements.txt
Berserker66 Feb 16, 2024
e74e9ed
Update requirements.txt
black-sliver Feb 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions requirements.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
colorama>=0.4.5
colorama>=0.4.6
websockets>=12.0
Copy link
Member Author

Choose a reason for hiding this comment

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

Suggested change
colorama>=0.4.6
colorama>=0.4.5

possibly broken on linux?

Copy link
Member

Choose a reason for hiding this comment

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

Nothing to do with colorama.

logger.info() simply does not print to stdout for me, but print() and logger.error() does. host.yaml says loglevel: "info", so that should be fine? Any ideas?

Copy link
Member Author

Choose a reason for hiding this comment

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

No. I guess you could breakpoint into the log function and see where it goes wrong? Again, on my system it all works fine.

Copy link
Member

Choose a reason for hiding this comment

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

Turns out if I add

logger.setLevel(logging.INFO)

right after

logger = logging.getLogger("Client")

I get messages. So it seems like logging.getLogger() has a separate minimum logging level?

PyYAML>=6.0.1
jellyfish>=1.0.3
jinja2>=3.1.2
jinja2>=3.1.3
schema>=0.7.5
kivy>=2.2.1
kivy>=2.3.0
bsdiff4>=1.2.4
platformdirs>=4.0.0
platformdirs>=4.1.0
certifi>=2023.11.17
cython>=3.0.6
cython>=3.0.8
cymem>=2.0.8
orjson>=3.9.10
orjson>=3.9.10
Loading