Planet Python
Python Insider: Python 3.12.3 and 3.13.0a6 released
It’s time to eclipse the Python 3.11.9 release with two releases, one of which is the very last alpha release of Python 3.13:
Python 3.12.3
300+ of the finest commits went into this latest maintenance release of the latest Python version, the most stablest, securest, bugfreeest we could make it.
https://www.python.org/downloads/release/python-3123/
Python 3.13.0a6
What’s that? The last alpha release? Just one more month until feature freeze! Get your features done, get your bugs fixed, let’s get 3.13.0 ready for people to actually use! Until then, let’s test with alpha 6. The highlights of 3.13 you ask? Well:
- In the interactive interpreter, exception tracebacks are now colorized by default.
- A preliminary, experimental JIT was added, providing the ground work for significant performance improvements.
- The (cyclic) garbage collector is now incremental, which should mean shorter pauses for collection in programs with a lot of objects.
- Docstrings now have their leading indentation stripped, reducing memory use and the size of .pyc files. (Most tools handling docstrings already strip leading indentation.)
- The dbm module has a new dbm.sqlite3 backend that is used by default when creating new files.
- PEP 594 (Removing dead batteries from the standard library) scheduled removals of many deprecated modules: aifc, audioop, chunk, cgi, cgitb, crypt, imghdr, mailcap, msilib, nis, nntplib, ossaudiodev, pipes, sndhdr, spwd, sunau, telnetlib, uu, xdrlib, lib2to3.
- Many other removals of deprecated classes, functions and methods in various standard library modules.
- New deprecations, most of which are scheduled for removal from Python 3.15 or 3.16.
- C API removals and deprecations. (Some removals present in alpha 1 were reverted in alpha 2, as the removals were deemed too disruptive at this time.)
(Hey, fellow core developer, if a feature you find important is missing from this list, let Thomas know. It’s getting to be really important now!)
https://www.python.org/downloads/release/python-3130a6/We hope you enjoy the new releases!
Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself, or through contributions to the Python Software Foundation or CPython itself.
Thomas “can you tell I haven’t had coffee today” Wouters
on behalf of your release team,
Ned Deily
Steve Dower
Pablo Galindo Salgado
Łukasz Langa
Mike Driscoll: Anaconda Partners with Teradata for AI with Python packages in the Cloud
Anaconda has announced a new partnership with Teradata to bring Python and R packages to Teradata VantageCloud through the Anaconda Repository.
But what does that mean? This new partnership allows engineers to:
- Rapidly deploy and operationalize AI/ML developed using open-source Python and R packages.
- Unlock innovation and the full potential of data at scale with a wide variety of Python and R functionality on VantageCloud Lake.
- Flexibly use packages and versions of their choice for large-scale data science, AI/ML and generative AI use-cases.
- Securely work with Python/R models into VantageCloud Lake with no intellectual property (IP) leakage.
Teradata VantageCloud Lake customers can download Python and R packages from the Anaconda Repository at no additional cost. Python packages are available immediately, and R packages will be released before the end of the year.
For more information about Teradata ClearScape Analytics, please visit Teradata.com.
Learn more about partnering with Anaconda here.
The post Anaconda Partners with Teradata for AI with Python packages in the Cloud appeared first on Mouse Vs Python.
Real Python: Generating QR Codes With Python
From restaurant e-menus to airline boarding passes, QR codes have numerous applications that impact your day-to-day life and enrich the user’s experience. Wouldn’t it be great to make them look good, too? With the help of this video course, you’ll learn how to use Python to generate beautiful QR codes for your personal use case.
In its most basic format, a QR code contains black squares and dots on a white background, with information that any smartphone or device with a dedicated QR scanner can decode. Unlike a traditional bar code, which holds information horizontally, a QR code holds the data in two dimensions, and it can hold over a hundred times more information.
In this video course, you’ll learn how to:
- Generate a basic black-and-white QR code
- Change the size and margins of the QR code
- Create colorful QR codes
- Rotate the QR code
- Replace the static background with an animated GIF
[ Improve Your Python With 🐍 Python Tricks 💌 – Get a short & sweet Python Trick delivered to your inbox every couple of days. >> Click here to learn more and see examples ]
Python Bytes: #378 Python is on the edge
PyBites: Adventures in Import-land, Part II
“KeyError: 'GOOGLE_APPLICATION_CREDENTIALS‘”
It was way too early in the morning for this error. See if you can spot the problem. I hadn’t had my coffee before trying to debug the code I’d written the night before, so it will probably take you less time than it did me.
app.py:
from dotenv import load_dotenv from file_handling import initialize_constants load_dotenv() #...file_handling.py:
import os from google.cloud import storage UPLOAD_FOLDER=None DOWNLOAD_FOLDER = None def initialize_cloud_storage(): """ Initializes the Google Cloud Storage client. """ os.environ["GOOGLE_APPLICATION_CREDENTIALS"] storage_client = storage.Client() bucket_name = #redacted return storage_client.bucket(bucket_name) def set_upload_folder(): """ Determines the environment and sets the path to the upload folder accordingly. """ if os.environ.get("FLASK_ENV") in ["production", "staging"]: UPLOAD_FOLDER = os.path.join("/tmp", "upload") os.makedirs(UPLOAD_FOLDER, exist_ok=True) else: UPLOAD_FOLDER = os.path.join("src", "upload_folder") return UPLOAD_FOLDER def initialize_constants(): """ Initializes the global constants for the application. """ UPLOAD_FOLDER = initialize_upload_folder() DOWNLOAD_FOLDER = initialize_cloud_storage() return UPLOAD_FOLDER, DOWNLOAD_FOLDER DOWNLOAD_FOLDER=initialize_cloud_storage() def write_to_gcs(content: str, file: str): "Writes a text file to a Google Cloud Storage file." blob = DOWNLOAD_FOLDER.blob(file) blob.upload_from_string(content, content_type="text/plain") def upload_file_to_gcs(file_path:str, gcs_file: str): "Uploads a file to a Google Cloud Storage bucket" blob = DOWNLOAD_FOLDER.blob(gcs_file) with open(file_path, "rb") as f: blob.upload_from_file(f, content_type="application/octet-stream")See the problem?
This was just the discussion of a recent Pybites article.
When app.py imported initialize_constants from file_handling, the Python interpreter ran
DOWNLOAD_FOLDER = initialize_cloud_storage()and looked for GOOGLE_APPLICATION_CREDENTIALS from the environment path, but load_dotenv hadn’t added them to the environment path from the .env file yet.
Typically, configuration variables, secret keys, and passwords are stored in a file called .env and then read as environment variables rather than as pure text using a package such as python-dotenv, which is what is being used here.
So, I had a few options.
I could call load_dotenv before importing from file_handling:
from dotenv import load_dotenv load_dotenv() from file_handling import initialize_constantsBut that’s not very Pythonic.
I could call initialize_cloud_storage inside both upload_file_to_gcs and write_to_gcs
def write_to_gcs(content: str, file: str): "Writes a text file to a Google Cloud Storage file." DOWNLOAD_FOLDER = initialize_cloud_storage() blob = DOWNLOAD_FOLDER.blob(file) blob.upload_from_string(content, content_type="text/plain") def upload_file_to_gcs(file_path:str, gcs_file: str): "Uploads a file to a Google Cloud Storage bucket" DOWNLOAD_FOLDER = initialize_cloud_storage() blob = DOWNLOAD_FOLDER.blob(gcs_file) with open(file_path, "rb") as f: blob.upload_from_file(f, content_type="application/octet-stream")But this violates the DRY principle. Plus we really shouldn’t be initializing the storage client multiple times. In fact, we already are initializing it twice in the way the code was originally written.
Going GlobalSo what about this?
DOWNLOAD_FOLDER = None def initialize_constants(): """ Initializes the global constants for the application. """ global DOWNLOAD_FOLDER UPLOAD_FOLDER = initialize_upload_folder() DOWNLOAD_FOLDER = initialize_cloud_storage() return UPLOAD_FOLDER, DOWNLOAD_FOLDERHere, we are defining DOWNLOAD_FOLDER as having global scope.
This will work here.
This will work here, because upload_file_to_gcs and write_to_gcs are in the same module. But if they were in a different module, it would break.
Why does it matter?
Well, let’s go back to how Python handles imports. Remember that Python runs any code outside of a function or class at import. That applies to variable (or constant) assignment, as well. So if upload_file_to_gcs and write_to_gcs were in another module and importing DOWNLOAD_FOLDER from file_handling,p it would be importing it while assigned a value of None. It wouldn’t matter that by the time it was needed, it wouldn’t be assigned to None any longer. Inside this other module, it would still be None.
What would be necessary in this situation would be another function called get_download_folder.
def get_download_folder(): """ Returns the current value of the Google Cloud Storage bucket """ return DOWNLOAD_FOLDERThen, in this other module containing the upload_file_to_gcs and write_to_gcs functions, I would import get_download_folder instead of DOWNLOAD_FOLDER. By importing get_download_folder, you can get the value of DOWNLOAD_FOLDER after it has been assigned to an actual value, because get_download_folder won’t run until you explicitly call it. Which, presumably wouldn’t be until after you’ve let initialize_cloud_storage do its thing.
I have another part of my codebase where I have done this. On my site, I have a tool that helps authors create finetunes of GPT 3.5 from their books. This Finetuner is BYOK, or ‘bring your own key’ meaning that users supply their own OpenAI API key to use the tool. I chose this route because charging authors to fine-tune a model and then charging them to use it, forever, is just not something that benefits either of us. This way, they can take their finetuned model and use it an any of the multiple other BYOK AI writing tools that are out there, and I don’t have to maintain writing software on top of everything else. So the webapp’s form accepts the user’s API key, and after a valid form submit, starts a thread of my Finetuner application.
This application starts in the training_management.py module, which imports set_client and get_client from openai_client.py and passes the user’s API key to set_client right away. I can’t import client directly, because client is None until set_client has been passed the API key, which happens after import.
from openai import OpenAI client = None def set_client(api_key:str): """ Initializes OpenAI API client with user API key """ global client client = OpenAI(api_key = api_key) def get_client(): """ Returns the initialized OpenAI client """ return clientWhen the function that starts a fine tuning job starts, it calls get_client to retrieve the initialized client. And by moving the API client initialization into another module, it becomes available to be used for an AI-powered chunking algorithm I’m working on. Nothing amazing. Basically, just generating scene beats from each chapter to use as the prompt, with the actual chapter as the response. It needs work still, but it’s available for authors who want to try it.
A Class ActNow, we could go one step further from here. The code we’ve settled on so far relies on global names. Perhaps we can get away with this. DOWNLOAD_FOLDER is a constant. Well, sort of. Remember, it’s defined by initializing a connection to a cloud storage container. It’s actually a class. By rights, we should be encapsulating all of this logic inside of another class.
So what could that look like? Well, it should initialize the upload and download folders, and expose them as properties, and then use the functions write_to_gcs and upload_file_to_gcs as methods like this:
class FileStorageHandler: def __init__(self): self._upload_folder = self._set_upload_folder() self._download_folder = self._initialize_cloud_storage() @property def upload_folder(self): return self._upload_folder @property def download_folder(self): return self._download_folder def _initialize_cloud_storage(self): """ Initializes the Google Cloud Storage client. """ os.environ["GOOGLE_APPLICATION_CREDENTIALS"] storage_client = storage.Client() bucket_name = #redacted return storage_client.bucket(bucket_name) def _set_upload_folder(self): """ Determines the environment and sets the path to the upload folder accordingly. """ if os.environ.get("FLASK_ENV") in ["production", "staging"]: upload_folder = os.path.join("/tmp", "upload") os.makedirs(upload_folder, exist_ok=True) else: upload_folder = os.path.join("src", "upload_folder") return upload_folder def write_to_gcs(self, content: str, file_name: str): """ Writes a text file to a Google Cloud Storage file. """ blob = self._download_folder.blob(file_name) blob.upload_from_string(content, content_type="text/plain") def upload_file_to_gcs(self, file_path: str, gcs_file_name: str): """ Uploads a file to a Google Cloud Storage bucket. """ blob = self._download_folder.blob(gcs_file_name) with open(file_path, "rb") as file_obj: blob.upload_from_file(file_obj)Now, we can initialize an instance of FileStorageHandler in app.py and assign UPLOAD_FOLDER and DOWNLOAD_FOLDER to the properties of the class.
from dotenv import load_dotenv from file_handling import FileStorageHandler load_dotenv() folders = FileStorageHandler() UPLOAD_FOLDER = folders.upload_folder DOWNLOAD_FOLDER = folders.download_folder Key take awayIn the example, the error arose because initialize_cloud_storage was called at the top level in file_handling.py. This resulted in Python attempting to access environment variables before load_dotenv had a chance to set them.
I had been thinking of module level imports as “everything at the top runs at import.” But that’s not true. Or rather, it is true, but not accurate. Python executes code based on indentation, and functions are indented within the module. So, it’s fair to say that every line that isn’t indented is at the top of the module. In fact, it’s even called that: top-level code, which is defined as basically anything that is not part of a function, class or other code block.
And top-level code runs runs when the module is imported. It’s not enough to bury an expression below some functions, it will still run immediately when the module is imported, whether you are ready for it to run or not. Which is really what the argument against global variables and state is all about, managing when and how your code runs.
Understanding top-level code execution at import helped solved the initial error and design a more robust pattern.
Next stepsThe downside with using a class is that if it gets called again, a new instance is created, with a new connection to the cloud storage. To get around this, something to look into would be to implement something called a Singleton Pattern, which is outside of the scope of this article.
Also, the code currently doesn’t handle exceptions that might arise during initialization (e.g., issues with credentials or network connectivity). Adding robust error handling mechanisms will make the code more resilient.
Speaking of robustness, I would be remiss if I didn’t point out that a properly abstracted initialization method should retrieve the bucket name from a configuration or .env file instead of leaving it hardcoded in the method itself.
Anwesha Das: Test container image with eercheck
Execution Environments serves us the benefits of containerization by solving the issues such as software dependencies, portability. Ansible Execution Environment are Ansible control nodes packaged as container images. There are two kinds of Ansible execution environments
-
Base, includes the following
- fedora base image
- ansible core
- ansible collections : The following set of collections
ansible.posix
ansible.utils
ansible.windows
-
Minimal, includes the following
- fedora base image
- ansible core
I have been the release manager for Ansible Execution Environments. After building the images I perform certain steps of tests to check if the versions of different components of the newly built correct or not. So I wrote eercheck to ease the steps of tests.
What is eercheck?eercheck is a command line tool to test Ansible community execution environment before release. It uses podman py to connect and work with the podman container image, and Python unittest for testing the containers.
eercheck is a command line tool to test Ansible Community Execution Environment before release. It uses podman-py to connect and work with the podman container image, and Python unittest for testing the containers. The project is licensed under GPL-3.0-or-later.
How to use eercheck?Activate the virtual environment in the working directory.
python3 -m venv .venv source .venv/bin/activate python -m pip install -r requirements.txtActivate the podman socket.
systemctl start podman.socket --userUpdate vars.json with correct version numbers.Pick the correct versions of the Ansible Collections from the .deps file of the corresponding Ansible community package release. For example for 9.4.0 the Collection versions can be found in here. You can find the appropriate version of Ansible Community Package here. The check needs to be carried out each time before the release of the Ansible Community Execution Environment.
Execute the program by giving the correct container image id.
./containertest.py image_idHappy automating.
Real Python: Python News: What's New From March 2024
While many people went hunting for Easter eggs, the Python community stayed active through March 2024. The free-threaded Python project reached a new milestone, and you can now experiment with disabling the GIL in your interpreter.
The Python Software Foundation does a great job supporting the language with limited resources. They’ve now announced a new position that will support users of PyPI. NumPy is an old workhorse in the data science space. The library is getting a big facelift, and the first release candidate of NumPy 2 is now available.
Dive in to learn more about last month’s most important Python news.
Free-Threaded Python Reaches an Important MilestonePython’s global interpreter lock (GIL) has been part of the CPython implementation since the early days. The lock simplifies a lot of the code under the hood of the language, but also causes some issues with parallel processing.
Over the years, there have been many attempts to remove the GIL. However, until PEP 703 was accepted by the steering council last year, none had been successful.
The PEP describes how the GIL can be removed based on experimental work done by Sam Gross. It suggests that what’s now called free-threaded Python is activated through a build option. In time, this free-threaded Python is expected to become the default version of CPython, but for now, it’s only meant for testing and experiments.
When free-threaded Python is ready for bigger audiences, the GIL will still be enabled by default. You can then set an environment variable or add a command-line option to try out free-threaded Python:
Read the full article at https://realpython.com/python-news-march-2024/ »[ Improve Your Python With 🐍 Python Tricks 💌 – Get a short & sweet Python Trick delivered to your inbox every couple of days. >> Click here to learn more and see examples ]
Zato Blog: Integrating with Jira APIs
Continuing in the series of articles about newest cloud connections in Zato 3.2, this episode covers Atlassian Jira from the perspective of invoking its APIs to build integrations between Jira and other systems.
There are essentially two use modes of integrations with Jira:
- Jira reacts to events taking place in your projects and invokes your endpoints accordingly via WebHooks. In this case, it is Jira that explicitly establishes connections with and sends requests to your APIs.
- Jira projects are queried periodically or as a consequence of events triggered by Jira using means other than WebHooks.
The first case is usually more straightforward to conceptualize - you create a WebHook in Jira, point it to your endpoint and Jira invokes it when a situation of interest arises, e.g. a new ticket is opened or updated. I will talk about this variant of integrations with Jira in a future instalment as the current one is about the other situation, when it is your systems that establish connections with Jira.
The reason why it is more practical to first speak about the second form is that, even if WebHooks are somewhat easier to reason about, they do come with their own ramifications.
To start off, assuming that you use the cloud-based version of Jira (e.g. https://example.atlassian.net), you need to have a publicly available endpoint for Jira to invoke through WebHooks. Very often, this is undesirable because the systems that you need to integrate with may be internal ones, never meant to be exposed to public networks.
Secondly, your endpoints need to have a TLS certificate signed by a public Certificate Authority and they need to be accessible on port 443. Again, both of these are something that most enterprise systems will not allow at all or it may take months or years to process such a change internally across the various corporate departments involved.
Lastly, even if a WebHook can be used, it is not always a given that the initial information that you receive in the request from a WebHook will already contain everything that you need in your particular integration service. Thus, you will still need a way to issue requests to Jira to look up details of a particular object, such as tickets, in this way reducing WebHooks to the role of initial triggers of an interaction with Jira, e.g. a WebHook invokes your endpoint, you have a ticket ID on input and then you invoke Jira back anyway to obtain all the details that you actually need in your business integration.
The end situation is that, although WebHooks are a useful concept that I will write about in a future article, they may very well not be sufficient for many integration use cases. That is why I start with integration methods that are alternative to WebHooks.
Alternatives to WebHooksIf, in our case, we cannot use WebHooks then what next? Two good approaches are:
- Scheduled jobs
- Reacting to emails (via IMAP)
Scheduled jobs will let you periodically inquire with Jira about the changes that you have not processed yet. For instance, with a job definition as below:
Now, the service configured for this job will be invoked once per minute to carry out any integration works required. For instance, it can get a list of tickets since the last time it ran, process each of them as required in your business context and update a database with information about what has been just done - the database can be based on Redis, MongoDB, SQL or anything else.
Integrations built around scheduled jobs make most sense when you need to make periodic sweeps across a large swaths of business data, these are the "Give me everything that changed in the last period" kind of interactions when you do not know precisely how much data you are going to receive.
In the specific case of Jira tickets, though, an interesting alternative may be to combine scheduled jobs with IMAP connections:
The idea here is that when new tickets are opened, or when updates are made to existing ones, Jira will send out notifications to specific email addresses and we can take advantage of it.
For instance, you can tell Jira to CC or BCC an address such as zato@example.com. Now, Zato will still run a scheduled job but instead of connecting with Jira directly, that job will look up unread emails for it inbox ("UNSEEN" per the relevant RFC).
Anything that is unread must be new since the last iteration which means that we can process each such email from the inbox, in this way guaranteeing that we process only the latest updates, dispensing with the need for our own database of tickets already processed. We can extract the ticket ID or other details from the email, look up its details in Jira and the continue as needed.
All the details of how to work with IMAP emails are provided in the documentation but it would boil down to this:
# -*- coding: utf-8 -*- # Zato from zato.server.service import Service class MyService(Service): def handle(self): conn = self.email.imap.get('My Jira Inbox').conn for msg_id, msg in conn.get(): # Process the message here .. process_message(msg.data) # .. and mark it as seen in IMAP. msg.mark_seen()The natural question is - how would the "process_message" function extract details of a ticket from an email?
There are several ways:
- Each email has a subject of a fixed form - "[JIRA] (ABC-123) Here goes description". In this case, ABC-123 is the ticket ID.
- Each email will contain a summary, such as the one below, which can also be parsed:
- Finally, each email will have an "X-Atl-Mail-Meta" header with interesting metadata that can also be parsed and extracted:
The first option is the most straightforward and likely the most convenient one - simply parse out the ticket ID and call Jira with that ID on input for all the other information about the ticket. How to do it exactly is presented in the next chapter.
Regardless of how we parse the emails, the important part is that we know that we invoke Jira only when there are new or updated tickets - otherwise there would not have been any new emails to process. Moreover, because it is our side that invokes Jira, we do not expose our internal system to the public network directly.
However, from the perspective of the overall security architecture, email is still part of the attack surface so we need to make sure that we read and parse emails with that in view. In other words, regardless of whether it is Jira invoking us or our reading emails from Jira, all the usual security precautions regarding API integrations and accepting input from external resources, all that still holds and needs to be part of the design of the integration workflow.
Creating Jira connectionsThe above presented the ways in which we can arrive at the step of when we invoke Jira and now we are ready to actually do it.
As with other types of connections, Jira connections are created in Zato Dashboard, as below. Note that you use the email address of a user on whose behalf you connect to Jira but the only other credential is that user's API token previously generated in Jira, not the user's password.
Invoking JiraWith a Jira connection in place, we can now create a Python API service. In this case, we accept a ticket ID on input (called "a key" in Jira) and we return a few details about the ticket to our caller.
This is the kind of a service that could be invoked from a service that is triggered by a scheduled job. That is, we would separate the tasks, one service would be responsible for opening IMAP inboxes and parsing emails and the one below would be responsible for communication with Jira.
Thanks to this loose coupling, we make everything much more reusable - that the services can be changed independently is but one part and the more important side is that, with such separation, both of them can be reused by future services as well, without tying them rigidly to this one integration alone.
# -*- coding: utf-8 -*- # stdlib from dataclasses import dataclass # Zato from zato.common.typing_ import cast_, dictnone from zato.server.service import Model, Service # ########################################################################### if 0: from zato.server.connection.jira_ import JiraClient # ########################################################################### @dataclass(init=False) class GetTicketDetailsRequest(Model): key: str @dataclass(init=False) class GetTicketDetailsResponse(Model): assigned_to: str = '' progress_info: dictnone = None # ########################################################################### class GetTicketDetails(Service): class SimpleIO: input = GetTicketDetailsRequest output = GetTicketDetailsResponse def handle(self): # This is our input data input = self.request.input # type: GetTicketDetailsRequest # .. create a reference to our connection definition .. jira = self.cloud.jira['My Jira Connection'] # .. obtain a client to Jira .. with jira.conn.client() as client: # Cast to enable code completion client = cast_('JiraClient', client) # Get details of a ticket (issue) from Jira ticket = client.get_issue(input.key) # Observe that ticket may be None (e.g. invalid key), hence this 'if' guard .. if ticket: # .. build a shortcut reference to all the fields in the ticket .. fields = ticket['fields'] # .. build our response object .. response = GetTicketDetailsResponse() response.assigned_to = fields['assignee']['emailAddress'] response.progress_info = fields['progress'] # .. and return the response to our caller. self.response.payload = response # ########################################################################### Creating a REST channel and testing itThe last remaining part is a REST channel to invoke our service through. We will provide the ticket ID (key) on input and the service will reply with what was found in Jira for that ticket.
We are now ready for the final step - we invoke the channel, which invokes the service which communicates with Jira, transforming the response from Jira to the output that we need:
$ curl localhost:17010/jira1 -d '{"key":"ABC-123"}' { "assigned_to":"zato@example.com", "progress_info": { "progress": 10, "total": 30 } } $And this is everything for today - just remember that this is just one way of integrating with Jira. The other one, using WebHooks, is something that I will go into in one of the future articles.
More blog posts➤EuroPython: EuroPython April 2024 Newsletter
Hello, Python enthusiasts! 👋
Guess what? We&aposre on the home stretch now, with less than 100 days left until we all rendezvous in the enchanting city of Prague for EuroPython 2024!
Only 91 days left until EuroPython 2024!Can you feel the excitement tingling in your Pythonic veins?
Let’s look up what&aposs been cooking in the EuroPython pot lately. 🪄🍜
📣 ProgrammeThe curtains have officially closed on the EuroPython 2024 Call for Proposals! 🎬
We&aposve hit records with an incredible 627 submissions this year!! 🎉
Thank you to each and every one of you brave souls who tossed your hats into the ring! 🎩 Your willingness to share your ideas has truly made this a memorable journey.
🗃️ Community VotingEuroPython 2024 Community Voting was a blast!
The Community Voting is composed of all past EuroPython attendees and prospective speakers between 2015 and 2024.
We had 297 people contributing, making EuroPython more responsive to the community’s choices. 😎 We can’t thank you enough for helping us hear the voice of the Community.
Now, our wonderful programme crew along with the team of reviewers and community voters have been working hard to create the schedule for the conference! 📋✨
💰 Sponsor EuroPython 2024EuroPython is a volunteer-run, non-profit conference. All sponsor support goes to cover the cost of running the Europython Conference and supporting the community with Grants and Financial Aid.
If you want to support EuroPython and its efforts to make the event accessible to everyone, please consider sponsoring (or asking your employer to sponsor).
Sponsoring EuroPython guarantees you highly targeted visibility and the opportunity to present your company to one of the largest and most diverse Python communities in Europe and beyond!
There are various sponsor tiers and some have limited slots available. This year, besides our main packages, we offer add-ons as optional extras. For more information, check out our Sponsorship brochure.
🐦 We have an Early Bird 10% discount for companies that sign up by April 15th.🐦More information at: https://ep2024.europython.eu/sponsor 🫂 Contact us at sponsoring@europython.eu
🎟️ Ticket SalesThe tickets are now open to purchase, and there is a variety of options:
- Conference Tickets: access to Conference and Sprint Weekends.
- Tutorial Tickets: access to the Workshop/Tutorial Days and Sprint Weekend (no access to the main conference).
- Combined Tickets: access to everything during the whole seven-day, i.e. workshops, conference talks and sprint weekend!
We also offer different payment tiers designed to answer each attendee&aposs needs. They are:
Business Tickets: for companies and employees funded by their companies- Tutorial Only Business (Net price €400.00 + 21% VAT)
- Conference Only Business (Net price €500.00 + 21% VAT)
- Late Bird (Net price €750.00 + 21% VAT)
- Combines Business (Net price €800.00 + 21% VAT)
- Late Bird (Net price €1200.00 + 21% VAT)
- Tutorial Only Personal (€200.00 incl. 21%VAT)
- Conference Only Personal (€300.00 incl. 21% VAT)
- Late Bird (€450.00 incl. 21% VAT)
- Combined Personal (€450.00 incl. 21% VAT)
- Late Bird (€675.00 incl. 21% VAT)
- Conference Only Education (€135.00 incl. 21% VAT)
- Tutorial Only Education (€100.00 incl. 21% VAT)
- Combined Education (€210.00 incl. 21% VAT)
Seize the chance to grab an EP24 ticket and connect with the delightful community of Pythonistas and happy locals this summer! ☀️
Need more information regarding tickets? Please visit https://ep2024.europython.eu/tickets or contact us at helpdesk@europython.eu.
⚖️ Visa ApplicationIf you require a visa to attend EuroPython 2024 in Prague, now is the time to start preparing.
The first step is to verify if you require a visa to travel to the Czech Republic.
The Czech Republic is a part of the EU and the Schengen Area. If you already have a valid Schengen visa, you may NOT need to apply for a Czech visa. If you are uncertain, please check this website and consult your local consular office or embassy. 🏫
If you need a visa to attend EuroPython, you can lodge a visa application for Short Stay (C), up to 90 days, for the purpose of “Business /Conference”. We recommend you do this as soon as possible.
Please, make sure you read all the visa pages carefully and prepare all the required documents before making your application. The EuroPython organisers are not able nor qualified to give visa advice.
However, we are more than happy to help with the visa support letter issued by the EuroPython Society. Every registered attendee can request one; we only issue visa support letters to confirmed attendees. We kindly ask you to purchase your ticket before filling in the request form.
For more information, please check https://ep2024.europython.eu/visa or contact us at visa@europython.eu. ✈️
💶 Financial AidWe are also pleased to announce our financial aid, sponsored by the EuroPython Society. The goal is to make the conference open to everyone, including those in need of financial assistance.
Submissions for the first round of our financial aid programme are open until April 21st 2024.
There are three types of grants including:
- Free Ticket Voucher Grant
- Travel/Accommodation Grant (reimbursement of travel costs up to €400.)
- Visa Application Fee Grant (up to €80)
If you apply for the first round and do not get selected, you will automatically be considered for the second round. No need to reapply.
8 March 2024Applications open21 April 2024Deadline for submitting first-round applications8 May 2024First round of grant notifications12 May 2024Deadline to accept a first-round grant19 May 2024Deadline for submitting second-round applications15 June 2024Second round of grant notifications12 June 2024Deadline to accept a second-round grant21 July 2024Deadline for submitting receipts/invoicesVisit https://europython.eu/finaid for information on eligibility and application procedures for Financial Aid grants.
🎤 Public Speaking Workshop for MenteesWe are excited to announce that this year’s Speaker Mentorship Programme comes with an extra package!
We have selected a limited number of mentees for a 5-week interactive course covering the basics of a presentation from start to finish.
The main facilitator is the seasoned speaker Cheuk Ting Ho and the participants will end the course by delivering a talk covering all they have learned.
We look forward to the amazing talks the workshop participants will give us. 🙌
🐍 Upcoming Events in EuropeHere are some upcoming events happening in Europe soon.
Czech Open Source Policy Forum: Apr 24, 2024 (In-Person)Interested in open source and happen to be near Brno/Czech Republic in April? Join the Czech Open Source Policy Forum and have the chance to celebrate the launch of the Czech Republic&aposs first Open Source Policy Office (OSPO). More info at: https://pretix.eu/om/czospf2024/
OSSCi Prague Meetup: May 16, 2024 (In-Person)Join the forefront of innovation at OSSci Prague Meetup, where open source meets science. Call for Speakers is open! https://pydata.cz/ossci-cfs.html
PyCon DE & PyData Berlin: April 22-24 2024Dive into three days of Python and PyData excellence at Pycon DE! Visit https://2024.pycon.de/ for details.
PyCon Italy: May 22-25 2024PyCon Italia 2024 will happen in Florence. The schedule is online and you can check it out at their nice website: https://2024.pycon.it/
GeoPython 2024: May 27-29, 2024GeoPython 2024 will happen in Basel, Switzerland. For more information visit their website: https://2024.geopython.net/
🤭 Py.JokesCan you imagine our newsletter without joy and laughter? We can’t. 😾🙅♀️❌ Here’s this month&aposs PyJoke:
pip install pyjokesimport pyjokesprint(pyjokes.get_joke()) How many programmers does it take to change a lightbulb? None, they just make darkness a standard! 🐣 See You All Next MonthBefore saying goodbye, thank you so much for reading this far.
We can’t wait to reunite with all you amazing people in beautiful Prague again.
Let me remind you how pretty Prague is during summer. 🌺🌼🌺
Rozkvetlá jarní Praha, březen 2024 by Radoslav VnenčákRemember to take good care of yourselves, stay hydrated and mind your posture!
Oh, and don’t forget to force encourage your friends to join us at EuroPython 2024! 😌
It’s time again to make new Python memories together!Looking forward to meeting you all here next month!
With much joy and excitement,
EuroPython 2024 Team 🤗
Python Insider: Python 3.11.9 is now available
This is the last bug fix release of Python 3.11
This is the ninth maintenance release of Python 3.11Python 3.11.9 is the newest major release of the Python programming language, and it contains many new features and optimizations. Get it here:
https://www.python.org/downloads/release/python-3119/
Major new features of the 3.11 series, compared to 3.10Among the new major new features and changes so far:
- PEP 657 – Include Fine-Grained Error Locations in Tracebacks
- PEP 654 – Exception Groups and except*
- PEP 673 – Self Type
- PEP 646 – Variadic Generics
- PEP 680 – tomllib: Support for Parsing TOML in the Standard Library
- PEP 675 – Arbitrary Literal String Type
- PEP 655 – Marking individual TypedDict items as required or potentially-missing
- bpo-46752 – Introduce task groups to asyncio
- PEP 681 – Data Class Transforms
- bpo-433030– Atomic grouping ((?>…)) and possessive quantifiers (*+, ++, ?+, {m,n}+) are now supported in regular expressions.
- The Faster Cpython Project is already yielding some exciting results. Python 3.11 is up to 10-60% faster than Python 3.10. On average, we measured a 1.22x speedup on the standard benchmark suite. See Faster CPython for details.
More resources
- PEP 664, 3.11 Release Schedule
- Report bugs at https://bugs.python.org.
A kugelblitz is a theoretical astrophysical object predicted by general relativity. It is a concentration of heat, light or radiation so intense that its energy forms an event horizon and becomes self-trapped. In other words, if enough radiation is aimed into a region of space, the concentration of energy can warp spacetime so much that it creates a black hole. This would be a black hole whose original mass–energy was in the form of radiant energy rather than matter, however as soon as it forms, it is indistinguishable from an ordinary black hole.
We hope you enjoy the new releases!Thanks to all of the many volunteers who help make Python Development and these releases possible! Please consider supporting our efforts by volunteering yourself or through organization contributions to the Python Software Foundation.https://www.python.org/psf/
Your friendly release team,
Ned Deily @nad
Steve Dower @steve.dower
Pablo Galindo Salgado @pablogsal
Python Morsels: Python's http.server module
Use Python's http.server module to serve up a static website on your own machine.
Table of contents
- A directory trees of index.html files
- Serving up HTML files with http.server
- Customizing http.server with CLI arguments
- Using http.server as a module
- Use python -m http.server for a local HTTP server
We have a directory here that represents a static website:
~/comprehensions/_build/dirhtml $ ls index.html index.htmlWe not only have an index.html file, but also a bunch of sub-directories, each with their own index.html file:
~/comprehensions/_build/dirhtml $ ls generator-expressions index.htmlThe only way to really navigate this website locally is to serve up these files using some sort of HTTP server that is aware of these index files.
Python comes bundled with an HTTP server that we can use. It's called http.server.
Serving up HTML files with http.serverIf we run this module …
Read the full article: https://www.pythonmorsels.com/http-server/PyBites: Python F-String Codes I Use Every Day
A few examples that will save the day probably* 95% of time.
*I don’t have the actual data but seriously, I bet you’ll find those tips useful more often than not!
IntroductionThis article was originally posted on Medium.
I use f-strings every day. The irony is I also every day end up searching the Web to find the correct format to use. Until one day I thought a better use of my time would be to create a cheat sheet of the most common formatting cases — AKA this article. It covers the following:
- integers, floats, numbers and scientific notation
- percentages %
- dates
- padding
- adding +/- sign in front of a number
It’s important to note that the f-strings were first introduced in Python 3.6 (PEP 498 if you REALLY must know) so make sure to check the Python version first, if things don’t work for you.
The formatThe most basic f-string format goes like this:
You can use this format to print numbers, texts, or even evaluate expressions.
author = "pawjast" year = 2022 print(f"Example 1: {author}") # string print(f"Example 2: {year}") # number print(f"Example 3: {2 + 2}") # expressionThe output:
Example 1: pawjast Example 2: 2022 Example 3: 4You might have noticed that the 2+2 expression in Example 3 got evaluated and 4 was printed.
You’ll get both, the name and the value if you add = sign to a variable.
text = "Data Science Blog" print(f"{text=}")The output:
text='Data Science Blog'Template below generalizes how you can add a specific format to a variable:
Next paragraphs shows examples of how to use it.
Recap on numbersLast stop before going any further. I’ll be using different ways of writing numbers later in the article so let’s review the most common ones.
int_1 = 1 int_with_separator = 1_000 # `int` with 1,000 separator float_1 = 1.125 float_2 = 3.50 scientific_1 = 1.23e2 # 1.23 * 10^2 print(f"Example 1 - int: {int_1}") print(f"Example 2 - int with _ as thousands separator: {int_with_separator}") print(f"Example 3 - float: {float_1}") print(f"Example 4 - float with trailing zero: {float_2}") print(f"Example 5 - float in scientific notation: {scientific_1}")The output:
Example 1 - int: 1 Example 2 - int with _ as thousands separator: 1000 Example 3 - float: 1.125 Example 4 - float with trailing zero: 3.5 Example 5 - float in scientific notation: 123.0You can observe that:
- floats had the trailing zeros truncated (Example 4)
- scientific notation was printed as a regular float
- the rest of the variables were printed “as is”
The float type is enforced by using code f. What you want to control in floats is the number of decimal places.
pi_val = 3.141592 print(f"Example 1: {pi_val:f}") print(f"Example 2: {pi_val:.0f}") print(f"Example 3: {pi_val:.1f}") print(f"Example 4: {pi_val:.3f}")The output:
Example 1: 3.141592 Example 2: 3 Example 3: 3.1 Example 4: 3.142Side note: f-strings are flexible enough to allow nesting.
float_val = 1.5 precision = 3 print(f"{float_val:.{precision}f}")The output:
1.500 PercentageUse code % to enforce percentage type. Percentage is still a float so you can still use .<whole_number> to control the precision.
val = 0.5 print(f"Example 1: {val:%}") print(f"Example 2: {val:.0%}")The output:
Example 1: 50.000000% Example 2: 50%More examples of controlling precision in %:
val = 1.255 print(f"Example 1: {val:.0%}") print(f"Example 2: {val:.1%}")The output:
Example 1: 125% Example 2: 125.5% Scientific notationIf you want scientific notation to be printed as such (and not as a regular float) it can be enforced with e or E code.
val = 1.23e3 # 1.23 * 10^3 print(f"Example 1: {val:e}") print(f"Example 2: {val:E}")The output:
1: 1.230000e+03 2: 1.230000E+03No surprise the precision can be controlled in this case too.
val = 1.2345e3 print(f"{val:.2e}")The output:
1.23e+03You can even print a regular number in scientific notation.
val = 2022 print(f"{val:.3e}")The output:
2.022e+03 IntegersIntegers are enforced using code d.
val = 1 print(f"{val:d}")The output:
1Adding , to the code will print the thousands separator.
int_1 = 1000 int_2 = 1000_000_000 print(f"{int_1:,d}") print(f"{int_2:,d}")The output:
1,000 1,000,000,000 NumbersIf the aim is to just print a number, you can use generic code — n.
val_int = 1 val_float = 1.234 val_scient = 4.567e2 print(f"{val_int =: n}") print(f"{val_float =: n}") print(f"{val_scient =: n}")The output:
val_int = 1 val_float = 1.234 val_scient = 456.7You can still use .<whole_number> format to control the precision.
Side note: in this case whole_number determines the total number of digits printed, not the number of decimal points! On top of that, n code will decide the best output format for a number.
val_float_1 = 1.234 val_float_2 = 20.234 val_float_3 = 123.456 print(f"{val_float_1 =: .2n}") # prints as truncated float print(f"{val_float_2 =: .2n}") # prints as int print(f"{val_float_3 =: .2n}") # prints as scientific notationThe output:
val_float_1 = 1.2 val_float_2 = 20 val_float_3 = 1.2e+02 Dates from datetime import date, datetimePrinting a date “as is” works exactly like printing any other variable.
day = date( year=2022, month=9, day=1 ) print(f"{day}")The output:
2022-09-01To recreate the format you will use the following codes:
- %Y for year
- %m for month
- %d for day
With those codes you can e.g. create a new date format.
print(f"{day:%Y-%m-%d}") # default appearance print(f"{day:%Y/%m/%d}") # use `/` as separatorThe output:
2022-09-01 2022/09/01It’s also possible to print a month as a text:
- %b — short version
- %B — long version
The output:
2022 Sep 01 2022 September 01The same variable can be printed multiple times.
print(f"{day:%b or %B}?") print(f"{day:%Y %Y %Y}"The output:
Sep or September? 2022 2022 2022Reusing the same variable can be useful e.g. when you want to print the date and provide the day of the week as text (using code %A ).
print(f"{day:%Y %b %d (%A)}")The outcome:
2022 Sep 01 (Thursday)Last but not least, you can swap %Y for %y to get short version of the year.
print(f"{day:%y.%m.%d}")The output:
22.09.01 DatetimeLet’s specify two datetime variables.
day_and_time = datetime( year=2022, month=9, day=1, hour=17, minute=30, second=45 ) now = datetime.now() print(f"{day_and_time}") print(f"{now}") # with mircosecondsThe output:
2022-09-01 17:30:45 2022-12-08 15:49:37.810347Time format requires the following codes:
- %H — hour
- %M — minute
- %S — second
- %f — millisecond (1s = 1000 milliseconds)
Therefore, the default format would look like below.
print(f"{now:%Y-%m-%d %H:%M:%S.%f}")The outcome:
2022-12-08 15:49:37.810347f-string obviously creates a string (try this code to confirm it: type(f”now:%Y-%m-%d %H:%M%S.%f}”)). Therefore, if e.g. you are not happy with the number of decimal points for milliseconds, you can easily truncate them.
print(f"{now:%Y-%m-%d %H:%M:%S.%f}"[:22])The output:
2022-12-08 15:49:37.81In order to change the 24hr format to 12hr format, you will need to:
- swap hour code from %H to %I
- Optionally add %p at the end if you want to add AM/PM to the time
The output:
24hr: 2022-09-01 17:30:45 12hr: 2022-09-01 05:30:45 12hr with AM/PM: 2022-09-01 05:30:45 PMFew more useful date formats:
- %j for day of the year
- %W for week of the year (assuming Monday as first day of the week)
- %U for week of the year (assuming Sunday as first day of the week
The outcome:
The date: 2018-09-17 Day of the year: 260 Week of the year (Mon): 38 Week of the year (Sun): 37 PaddingPadding with empty spaces.
val = 1 print(f"1: {val:1d}") print(f"2: {val:2d}") print(f"3: {val:3d}")The output:
1: 1 2: 1 3: 1Padding with zeros.
val = 1 print(f"1: {val:01d}") print(f"2: {val:02d}") print(f"3: {val:03d}")The output:
1: 1 2: 01 3: 001I usually use zero — padding with for loop to keep the text nicely aligned in the terminal.
for i in range(11): print(f"{i:02d}")The output:
01 02 ... 09 10 Positive/negative signIn some cases you will require to show a +/- sign next to a number.
positive = 1.23 negative = -1.23 print(f"1: {positive:+.2f} {negative:+.2f}") print(f"2: {positive:-.2f} {negative:-.2f}") print(f"3: {positive: .2f} {negative: .2f}")The output:
1: +1.23 -1.23 2: 1.23 -1.23 3: 1.23 -1.23 Combining all things together # print variable with name, limit precision and thousands separator val = 11500.23456 print(f"{val = :,.3f}")The output:
val = 11,500.235We’re done .
Full code Connect with meMedium Twitter / X GitHub Substack LinkedIn
Resources1⃣ https://docs.python.org/3/reference/lexical_analysis.html#f-strings
2⃣ https://docs.python.org/3/library/string.html#format-specification-mini-language