For those who've been following the #Python Functions Series, today we'll take a short break and Day 10 will return tomorrow – There's still a related-thread later today, but not directly part of the series.
So far we've covered:
• terminology (boring but useful)
• …
• Choosing to use arguments as either positional or keyword
• Using optional arguments by assigning default values
• *args and **kwargs, or variable number of positional and keyword arguments
• Using positional-only arguments, or the "rogue" forward slash / in functions
• …
• Using keyword-only arguments, or the "rogue" asterisk * in function signatures
Next up:
• type hinting
• general best-practices when defining and using functions
@s_gruppetta Why don't you make use of this server's wonderful feature of being able to have one big post? It's a bit spammy this way and makes it less readable.
If you insist on seperating your posts up like that, I'd suggest to have your first post be public and subsequent ones be unlisted (since they're threaded the first post will suffice to be publicly shown).
@trinsec Separating into separate posts makes them more bite-sized and more digestible. I don't think I like the idea of long posts, personally, although I can see rare instances where that may be useful
@s_gruppetta But that's where markdown, with headers and such, come in use. It'll be bite-sized that way.
Plus your bite-sized posts seem to cut off at weird spots. A list that gets cut off instead of letting it be listed fully in one post?
@trinsec As for making only the first one listed, I've experimented with this on one thread and I'll do it one ones I write directly here. But others come from an existing workflow and are posted automatically, so until there's a setting to make this default on all threads (that would be a great setting to have!), it may be tricky