Source needed because the Rust library is bigger than the STL, no one cares about print being a macro, and derivation being an issue only applies when you compare Rust to scripting languages.
Rust is a contender to C and C++, not Visual Basic that can do everything poorly.
A lot of things that would normally be part of the language
Give examples because println is not convincing. Why would you have println on an embedded system that has no display?
We used to say RTFM or Lurk more in the good old days.
In a recent post on HackerNews, someone said that there is no burden of proof that it works. The purest form of “trust me bro.”
2 comments and 7 posts: make a new account.
I’m pretty sure the awful formatting of the comment is here to trigger us.
Anyway, merge request rejected for that alone.
Rust meme I guess. You borrow through a reference, and references have the & symbol like C++.
Yet another subscription. Yet another habit tracker. No terms of service or privacy policy.
Better how?
Why put all the Python code in the script?
Yes. You can say "Session\\Port (lots of space here) = 12345"(formatting sucks, sorry) to align your values properly. Also are you sure that there is a double backslash here because you are using a raw string here?
Yes (and I’m sorry for not having more time to study this but):
logDateTime
That thing should be automatically printed by the logger somehow (most of the time, timestamps and log levels are inside the logger itself). If it’s not, check the configuration of the logger. Anyway. logDateTime has got to go. IMHO a logger is a magical object that you don’t control. It’s the user of the application who should set the rules one way or the other, like:
logger.info("qbittorrent listen port set to...
IIRC the logger can be set from the command-line, which you don’t control anyway. It’s the same thing in C++ and with any library on the planet (trust me), someone sets up the logging system for you outside of the application (in the main function or on the command-line or with environment variables or in a library/DLL) and all you can do is call “log.debug()” or “log.warning()” and hope for the best. Some libraries have huge systems to handle logs (rotating logs, serial ports, files, network…) and you shouldn’t give yourself headaches while using those things. Think of a logger as a pre-configured system that does way more that you should and want to know.
logger = logging.getLogger(…
Put that outside of main, after the imports. You can prepend it with an underscore to show that it’s a “private or protected” object belonging to your module. If it’s in main, you can’t use it in the other functions. You should do something like:
from qbittorrent import Client
_logger = logging.getLogger(...)
This way your logger is independent on whether you’re using it from the command line (with main) or not (with an import).
QB_PASSWORD
Same thing with all the QB_ variables IF they don’t change, you can put them globally for such a module, like _QB_PASSWORD = ... and use it everywhere if your module were to change in the future. But only if the variables are constants across the usage of the script.
a40124291102d
Last but not least, use argparse if you can, it’s a simple module to handle command-line arguments. I guess that the container ID can change, you can either detect it with the subprocess module, or write def get_current_forwarded_port(container_id = "a40124291102d"): or use argparse. Feel free to ask if argparse if too weird, but it’s the best module out there and it’s built-in.
TL;DR:
Anyway, great job, writing weird stuff for my own needs is how I started coding. Have fun.
Make the logger a global variable. This may be the only case where its acceptable to be global. And remove the log function. You can call the logger directly.
Also wrap the main code (after BEGIN SCRIPT) in a main function.
Last but not least log everything to the standard output (logging should do that by default), or configure the path in main(), it’s cleaner. If you log to stdout, the shell can redirect the logs to any path like python script.py > mylogs.txt
Make a 2 hours video of the UI and watch it.
Given these positive signals
Those idiots waited for 4 years because they followed the hype of the moment. I’m glad I removed Google from my life.
A nonprofit with a vetting process and weekly meetings is way too complex and/or serious for me. But good luck anyway.
It feels very complicated. The whole theory is better explained with any Lisp.
a portion of the community views complexity as a badge of honour
Developers have to eat. You can pay or do it yourself.
Same as usual. Companies will still use it because there is no “alternative,” and I’ll keep on using Linux at home and macOS at work. I grew up with Windows 3.1, it was fun, but I haven’t used Windows for the past 15 years (the last one being Windows 7 IIRC and it was a shitshow to program and administrate) and I’m a happy man now that I left that crap behind me.
Kotlin. The end.
You should go back to the basics of computer science if you don’t know the difference between lists, maps, sets, and tuples.