We're excited to announce our next speaker, Jacek Kołodziej! Join us as he dives into the intriguing world of Python's GIL 🐍💡. Curious about its impact? Wondering if you should care? Don't miss this insightful talk! 🗣️🇪🇪 #PyConEstonia2023#PythonGIL@Unit03
What's up with #CPython's #GIL in 2023?
I will be presenting its:
* past
* present (including how to deal with it)
* and (non-?)future
at @PyConEstonia next week. :)
https://t.co/41Ffq9bnre
#python
[PL only] Na dzisiejszym (18:00) @allegrotech Live będę mówił o tym, jak żyje się nam w zespole używającym na co dzień i Pythona, i stosów JVMowych. https://t.co/V5H0ODUH0L
Transmisja na Fb i YT https://t.co/vEziiDC5Wa. Zapraszam 😊
I published something! A high-level overview of managing dependencies in a #Python project https://t.co/kLq1S8yFXh
Yes ✅ it distinguishes libraries from applications.
Let me know what you think 🤗
[Polish only] Za 40 minut będę mówił o tym, jak wybrać między Scalą a Pythonem przy korzystaniu z Apache Spark ✨ 18:20, ścieżka ML & Big Data ("Fantastyka"), zapraszam🤗
We are live now with 5 Tracks at Allegro Tech Meeting 2021!
Software: https://t.co/AmGjcM0CHY
Infrastructure: https://t.co/YM2Jyd2XRN
UX & Product: https://t.co/HNS2F2reTe
ML & Big Data: https://t.co/s5MVhQla54
Security: https://t.co/PZMU2GXEoT
Anyone willing to mentor on #grafana , #prometheus, and #observability in #AWS context?
I'm new to the topic and in a desperate need to conquer the learning curve. Pretty please?
#Python The default branch on the CPython repo has just been changed to `main`.
I've updated my local clone of CPython, and you can do it too!
Here's my the asciinema showing how to do it:
https://t.co/IonVElTSdg
And here's the instructions on DevGuide
https://t.co/ZXTJGslPEE
Python 3.8.10 is the last regular bugfix release for the 3.8 series, moving to security fix-only mode.
Upgrade to 3.9 to keep receiving bugfixes, preferably to 3.9.5.
With 3.10.0 beta 1 you're invited to test-drive your projects with 3.10.
All out now:
https://t.co/wllBB49uV6
@Hamatti@0lpeh Me too. :) It's just good commit msgs have their value, clean code has its value, well prepared features have their value, features shipped early have their value etc. - and time off has its value too. I'm trying to see how to strike a balance there.
_That being said_, there's another question: how much do you _actually_ value the commit messages and orderly commit history in general?
Where do you strike a balance between the maintenance cost vs. value the commit history provides?
Any good articles about it?
@peter_podgorski There's a third way: shape the individual commits to 1) be atomic* changes that 2) best explain the context and the "why" of the change in the long run.
The exact tool (squashing, rebasing, cherry-picking) is less important, use whatever you like.
That's where my question came from. :) How to value the repo history maintenance against the rest of the maintenance, assuming the time being a limited resource ('cause it is ;) ).
1. I'm absolutely pro having a clean repo history with a lot of "why" and context in commit msgs
2. I'm doing it myself pretty much everywhere (company/open source, doesn't matter)
3. The more I do it, the more proficient I am, the less obstacles for doing it more