Press "Enter" to skip to content

Month: October 2026

What’s New in Python 3.15

Russ Hyde has some new release notes:

It’s October, so that means a new stable release of Python has arrived. Here we will review some of the changes introduced in Python 3.15.

Prominent changes in Python 3.15 that we will cover:

  • profiling & statistical sampling
  • lazy imports
  • unpacking * in for comprehensions

Click through to learn more about what’s out. Though I will say that I’m mostly on 3.13 and sometimes 3.14 because it can take a while for package makers to catch up.

Leave a Comment

Fabric Tenant Settings to Check at Launch

Paul Turley continues a series on Microsoft Fabric:

Article 3 covered the headline settings almost every tenant touches first, but the full tenant settings screen runs past 30 categories, from information protection to advanced networking. You won’t master all of it on day one, but knowing what’s there keeps you from being caught flat-footed later. Skim the full list once, even if you’re not ready to configure most of it, just so nothing surprises you when a business unit asks for a capability you didn’t know existed.

Click through for six tips.

Leave a Comment

A First Look at Microsoft Fabric On-Demand Capacity

Reitse Eskens gives it a try:

You can compare it to Serverless SQL databases: when it’s not in use, it won’t cost anything. Storage will always incur some cost, but no compute.
First, be aware that there are no reservations (reserve plans soon) available. Second, pricing to use items will differ from the regular capacities. Some items may have the same price; others will be calculated at x2 or x3. We have to wait for the official documentation to find out what the actual prices will be.

Right now, we don’t know what the cost will look like, though once the documentation is available, we should have a better idea. Assuming it’s not in some inscrutable units.

Leave a Comment

Query Plan Hints in Postgres 19

Elizabeth Garrett Christensen says you may not need it:

For years the Postgres community was against adding support for hints. They felt if you had correctly analyzed tables, the Postgres query planner would make the right choice. And they’re not wrong, for the most part. Yet many DBAs and developers will tell you of a time when a plan suddenly changed or something was saved by a hint. We can debate the good and bad elements of hints, but the cool thing is that you will soon have a choice in Postgres 19+.

Read on to see how plan hints will work and what you should try before using them.

Leave a Comment