I wanted a way that didn't depend on legacy API keys to get my morning podcast feed. NPR, annoyingly, does not provide a podcast feed for Morning Edition.
This tool creates a feed from scraping NPR's website. It's a bit limited, in that it does not go back in time farther than the NPR archive page for ME, which, at time of writing is 5 days, but it fulfills my needs.
It also puts the little funny stories higher in my app (Podcast Addict), by faking a timestamp for those shows an hour later than the other, because I like the funny bits first.
This is intended for personal use. It's not a performant implementation, and will probably run up you AWS bill if you hand out the URL and/or don't enable a pretty low throttling rate. This may be an issue for me, even
This will also cost you (very little) money. You can use the AWS free plan for a year, and after that, this method will cost you a handful of pennies per year
A note on Weekend Edition: This is also sloppily implemented, where it only uses the day of the week on which the script is run to decide if it should pull from Weekend Edition. This means that if you don't run it on a weekend, you won't get the weekend edition feed.

I created this to be run as an AWS lambda function, which can be used via API gateway. There are scripts in the repo that are designed to be used with the AWS CLI to update the lambda function.
You will need to have the AWS CLI installed for most of these to work. If you're running Windows, you're already doing it wrong.

update.sh - Update your lambda function. This create a .zip file with the dependencies required for the script to run, and upload the package to AWS Lambda. This may not work if you're running something other than 64-bit Linux.
run.sh - Run the lambda function from AWS
run.py - Test the script locally
function.py - The heavy lifting. This does the work to scrape NPR's site and creating the feed

I'll caveat this by saying, I'm by no means an AWS expert. Here's what I did:

1. Create the AWS Lambda function, and call it morning-edition. Make sure it's in the default region configured when you did aws configure. Configure this as a GET event.
2. This is a long-ish running function. Increase your Lambda timeout to ~10 seconds. For my use case, which is personal, this is fine.
3. Create an API gateway function that uses your lambda, and make sure it uses the GET method.
4. Make a mapping template in API gateway for application/rss+xml. Delete the others.
5. Paste the following into the mapping template, otherwise your API will return the XML enclosed in quotes, which will break things: $input.path('$')
6. For the Integration Request portion of API gateway, point it to your Lambda function. In my case, morning-edition
7. In order to use run.sh and update.sh, you'll need to configure the AWS CLI with credentials. You can create those in AWS IAM. I created a user called lambda-cli, and attached it to the groups AWSLambdaFullAccess and lambda-list-functions.
8. From there, you'll just need to run aws configure and copy-paste some things. Make sure your AWS region matches that of the user, lambda function, and the gateway - Not sure if all of those are strictly necessary, but that's what I did.

That's probably it... If you have issues, feel free to ask questions, or contribute.