202: Using Towncrier to Keep a Changelog
Test and Code
by Brian Okken
1d ago
Hynek joins the show to discuss towncrier. At the top of the towncrier documentation, it says "towncrier is a utility to produce useful, summarized news files (also known as changelogs) for your project." Towncrier is used by "Twisted, pytest, pip, BuildBot, and attrs, among others." This is the last of 3 episodes focused on keeping a CHANGELOG. Episode 200 kicked off the series with keepachangelog.com and Olivier Lacan In 201 we had Ned Batchelder discussing scriv. Special Guest: Hynek Schlawack. Links: Towncrier docs How to Keep a Changelog in Markdown - Towncrier docs Keep a Changelog stru ..read more
Visit website
201: Avoid merge conflicts on your CHANGELOG with "scriv"
Test and Code
by Brian Okken
1w ago
Last week we talked about the importance of keeping a changelog. This week we talk with Ned Batchelder about scriv, a tool to help maintain that changelog. Scriv "is a command-line tool for helping developers maintain useful changelogs. It manages a directory of changelog fragments. It aggregates them into entries in a CHANGELOG file." Special Guest: Ned Batchelder. Sponsored By: porkbun: A refreshingly different domain name registrar. Get a free .app or .dev domain name by using this link or promo code. Promo Code: TESTANDCODE Links: nedbat/scriv: Changelog management tool ..read more
Visit website
200: Keep a CHANGELOG
Test and Code
by Brian Okken
2w ago
A changelog is a file which contains a curated, chronologically ordered list of notable changes for each version of a project. This episode is about what a changelog is, with an interview with Olivier Lacan, creator of keepachangelog.com. The next two episodes talk about some tools to help software project teams keep changelogs while avoiding merge conflicts. Special Guest: Olivier Lacan. Sponsored By: porkbun: A refreshingly different domain name registrar. Get a free .app or .dev domain name by using this link or promo code. Promo Code: TESTANDCODE Links: Shields.io Keep a Changelog "The ..read more
Visit website
199: Is Azure Right for a Side Project?
Test and Code
by Brian Okken
1M ago
For a web side project to go from "working on desktop" to "live in the cloud", one decision that needs to be made is where to host everything. One option is Microsoft Azure. Lots of corporate sites use it. Is it right for side projects? Pamela Fox, a Cloud Advocate for Python at Microsoft, joins the show to help us with that question. Special Guest: Pamela Fox. Sponsored By: porkbun: A refreshingly different domain name registrar. Get a free .app or .dev domain name by using this link or promo code. Promo Code: TESTANDCODE Links: Python Bytes Episode #323 pamelafox gitHub projects Deploy a ..read more
Visit website
198: Testing Django Web Applications
Test and Code
by Brian Okken
1M ago
Django has some built in ways to test your application. There's also pytest-django and other plugins that help with testing. Carlton Gibson and Will Vincent from the Django Chat Podcast join the show to discuss how to get started testing your Django application. 00:00 Introduction 00:20 Thanks porkbun for sponsoring 01:41 Welcome and podcasting discussion 17:21 Django starter projects 21:35 Testing Django Should be chapters there also, if your podcast player supports them. Special Guests: Carlton Gibson and Will Vincent. Sponsored By: porkbun: A refreshingly different domain name registrar. G ..read more
Visit website
197: Python project trove classifiers - Do you need this bit of pyproject.toml metadata?
Test and Code
by Brian Okken
2M ago
Classifiers are one bit of Python project metadata that predates PyPI. Classifiers are weird. They were around in setuptools days, and are still here with pyproject.toml. What are they? Why do we need them? Do we need them? Which classifiers should I include? Why are they called "trove classifiers" in the Python docs Brett Cannon joins the show to discuss these wacky bits of metadata. Here's an example, from pytest-crayons: [project] ... classifiers = [ "License :: OSI Approved :: MIT License", "Framework :: Pytest" ] Special Guest: Brett Cannon. Sponsored By: Patreon Suppor ..read more
Visit website
196: I am not a supplier
Test and Code
by Brian Okken
2M ago
Should we think of open source components the same way we think of physical parts for manufactured goods? There are problems with supply chain analogy when applied to software. Thomas Depierre discusses some of those issues in this episode. Special Guest: Thomas Depierre. Links: I am not a supplier - article ..read more
Visit website
195: What would you change about pytest?
Test and Code
by Brian Okken
3M ago
Anthony Sottile and Brian discuss changes that would be cool for pytest, even unrealistic changes. These are changes we'd make to pytest if we didn't ahve to care about backwards compatibilty. Anthony's list: The import system Multi-process support out of the box Async support Changes to the fixture system Extend the assert rewriting to make it modular Add matchers to assert mechanism Ban test class inheritance Brian's list: Extend assert rewriting for custom rewriting, like check pytester matchers available for all tests Throw out nose and unittest compatibility plugins Throw out setup_mod ..read more
Visit website
194: Test & Code Returns
Test and Code
by Brian Okken
3M ago
A brief discussion of why Test & Code has been off the air for a bit, and what to expect in upcoming episodes. Links: Python Testing with pytest, 2nd Edition Getting started with pytest Online Course Software Testing with pytest Training Python Bytes Podcast ..read more
Visit website
193: The Good Research Code Handbook - Patrick Mineault
Test and Code
by Brian Okken
9M ago
I don't think it's too much of a stretch to say that software is part of most scientific research now. From astronomy, to neuroscience, to chemistry, to climate models. If you work in research that hasn't been affected by software yet, just wait. But how good is that software? How much of common best practices in software development are making it to those writing software in the sciences? Patrick Mineault has written "The Good Research Code Handbook". It's a website. It's concise. And it will put you on the right path to writing better software. Even if you don't write science based software ..read more
Visit website

Follow Test and Code on Feedspot

Continue with Google
Continue with Apple
OR