Restructuring data, the Python way.

>>> import glom
>>> glom.assign({}, "a.b.c.d", 42, missing=dict)
{'a': {'b': {'c': {'d': 42}}}}

# Path-based access for nested structures
>>> target = {'a': {'b': {'c': 'd'}}}
>>> glom(target, 'a.b.c') 
'd'

happy glomming! 😋

https://glom.readthedocs.io/en/latest/

Note #68: The Rules of Optimization Club

1. You do not optimize.
2. You do not optimize, without measuring first.
3. When the performance is not bound by the code, but by external factors, the optimization is over.
4. Only optimize code that already has full unit test coverage.
5. One factor at a time.
6. No unresolved bugs, no schedule pressure.
7. Testing will go on as long as it has to.
8. If this is your first night at Optimization Club, you have to write a test case.

from https://wiki.c2.com/?RulesOfOptimizationClub

PEP 622 -- Structural Pattern Matching

Interesting proposal for python 3.10.

The proposed indentation structure is as following:

match some_expression:
    case pattern_1:
        ...
    case pattern_2:
        ...

and example from pep:

match number:
    case 0:
        print("Nothing")
    case 1:
        print("Just one")
    case 2:
        print("A couple")
    case -1:
        print("One less than nothing")
    case 1-1j:
        print("Good luck with that...")

https://www.python.org/dev/peps/pep-0622/

Asynchronous IO Support for Core and ORM

SQLAlchemy 1.4 now supports Python asyncio-compatible database drivers using an all-new asyncio front-end interface to Connection for Core usage as well as Session for ORM use, using the AsyncConnection and AsyncSession objects.

https://docs.sqlalchemy.org/en/14/changelog/migration_14.html#asynchronous-io-support-for-core-and-orm

Note #71 The seven rules of a great Git commit message

1. Separate subject from body with a blank line
2. Limit the subject line to 50 characters
3. Capitalize the subject line
4. Do not end the subject line with a period
5. Use the imperative mood in the subject line
6. Wrap the body at 72 characters
7. Use the body to explain what and why vs. how

https://chris.beams.io/posts/git-commit/

Python 3.9 is around the corner

https://lwn.net/SubscriberLink/831783/8afbf1812decf4d9/

Hypermodern Python 👩‍🚀 🐍

Chapter 1: Setup
Chapter 2: Testing
Chapter 3: Linting
Chapter 4: Typing
Chapter 5: Documentation
Chapter 6: CI/CD

https://cjolowicz.github.io/posts/hypermodern-python-01-setup/

Airflow 2.0 ->

https://www.astronomer.io/blog/introducing-airflow-2-0/

Interesting thread how to solve interview problem https://twitter.com/al_grigor/status/1357028887209902088?s=21

Armin dislikes new PEP regarding structural pattern matching https://twitter.com/mitsuhiko/status/1359263135304187910
btw PEP has been approved!

https://www.python.org/dev/peps/pep-0636/

I can't recall where I saw this originally, but you can use the spaceship operator "--0--" to turn floor division into ceiling division:

>>> 12//5
2
>>> --0-- 12//5
3

There's also the ++0++ operator when you want to emphasize that you really *do* mean floor division:

>>> ++0++ 12//5
2


from https://bugs.python.org/issue43255#msg387248
But yes, -(-n // d) is the easy (if a little bit cryptic) way to get the ceiling of n / d.

It's just a trick

It's because unary minus is right-associative and binds tighter than binary minus which is left-associative

-12 // 5 => - 3
- (-12 // 5) => +3
The rest is just putting 0 at the start:
--0 == 0
and --0--12//5 is parsed as
-(-(0)) - (- (12 // 5))

from Twitter https://twitter.com/ericpromislow/status/1362475189125095425?s=21

https://talkpython.fm/episodes/show/332/robust-python is a really interesting episode, and resonates really strongly with me for how to write good/maintainable/robust code

How to Make Your Code Reviewer Fall in Love with You:

1. Review your own code first
2. Write a clear change list description
3. Automate the easy stuff
4. Answer questions with the code itself
5. Narrowly scope changes
6. Separate functional and non-functional changes
7. Break up large change lists
8. Respond graciously to critiques
9. Be patient when your reviewer is wrong
10. Communicate your responses explicitly
11. Artfully solicit missing information
12. Award all ties to your reviewer
13. Minimize lag between rounds of review

https://mtlynch.io/code-review-love/

https://stop.lying.cloud/ 🤪

Introduction to OWASP Top 10 2021

https://owasp.org/Top10/