<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Python on Curiosettee</title>
    <link>https://curiosettee.net/topics/python/</link>
    <description>Recent content in Python on Curiosettee</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://curiosettee.net/topics/python/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Schedule Your Jupyter Notebook to Run Regularly in a Windows Server</title>
      <link>https://curiosettee.net/tutorials/schedule-a-python-script-on-windows-server/</link>
      <pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://curiosettee.net/tutorials/schedule-a-python-script-on-windows-server/</guid>
      <description>Jupyter notebooks give control and versatility to the Python inclined data analyst. And I personally like how it allows me to run the code cell by cell and provide annotations as I build. Having that control on inspecting the script as it develops is one of the powerful features of using Jupyter notebooks.
But once you are done with cell by cell control and you are now ready to set this script to run on a schedule, native Python scripts start to win and in a Windows environment, the Task Scheduler App allows you to do exactly that.</description>
    </item>
  </channel>
</rss>
