BEGIN:VCALENDAR
VERSION:2.0
PRODID:IEEE vTools.Events//EN
CALSCALE:GREGORIAN
BEGIN:VTIMEZONE
TZID:America/Chicago
BEGIN:DAYLIGHT
DTSTART:20260308T030000
TZOFFSETFROM:-0600
TZOFFSETTO:-0500
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZNAME:CDT
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251102T010000
TZOFFSETFROM:-0500
TZOFFSETTO:-0600
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZNAME:CST
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTAMP:20251218T135905Z
UID:BA2D8BDA-A596-423A-BED0-7B1FE6699287
DTSTART;TZID=America/Chicago:20251217T120000
DTEND;TZID=America/Chicago:20251217T130000
DESCRIPTION:Pixi is a modern\, single‑file‑driven package manager that 
 brings together the speed of lock‑file‑based installers and the reprod
 ucibility of the conda ecosystem. By declaring dependencies in a clear p
 ixi.toml and generating a deterministic pixi.lock\, Pixi guarantees iden
 tical environments on every machine while letting you pull packages from b
 oth conda‑forge and PyPI. Its built‑in solver eliminates version‑con
 flict headaches\, and the same file also defines isolated environments\, r
 eusable scripts\, and task runners\, making it ideal for data‑science\, 
 ML\, and general Python projects.\n\nIn the talk I&#39;ll walk through:\n\n- I
 nstallation – a one‑line curl/conda/pip bootstrap.\n- Demo – creatin
 g a project\, adding dependencies\, and inspecting the generated lock file
 .\n- Running tasks – using pixi run to execute scripts\, tests\, and CI 
 commands defined in the TOML.\n- Managing multiple environments – switch
 ing between dev\, test\, and production stacks with a single configuration
 .\n\nThe goal is to show how Pixi streamlines setup\, reproducibility\, an
 d automation from a local workstation all the way through CI/CD pipelines.
 \n\nRoom: CR-111\, 8800 Redstone Gateway SW #100\, Huntsville\, Alabama\, 
 United States\, 35808
LOCATION:Room: CR-111\, 8800 Redstone Gateway SW #100\, Huntsville\, Alabam
 a\, United States\, 35808
ORGANIZER:josh.langford@ieee.org
SEQUENCE:64
SUMMARY:Pixi: Package Management Made Easy
URL;VALUE=URI:https://events.vtools.ieee.org/m/522820
X-ALT-DESC:Description: &lt;br /&gt;&lt;p&gt;Pixi is a modern\, single‑file‑driven 
 package manager that brings together the speed of lock‑file‑based inst
 allers and the reproducibility of the conda ecosystem. By declaring depend
 encies in a clear pixi.toml and generating a deterministic pixi.lock\,
  Pixi guarantees identical environments on every machine while letting you
  pull packages from both conda‑forge and PyPI. Its built‑in solver eli
 minates version‑conflict headaches\, and the same file also defines isol
 ated environments\, reusable scripts\, and task runners\, making it ideal 
 for data‑science\, ML\, and general Python projects.&lt;/p&gt;\n&lt;p&gt;In the talk
  I&#39;ll walk through:&lt;/p&gt;\n&lt;ul&gt;\n&lt;li&gt;Installation &amp;ndash\; a one‑line curl
 /conda/pip bootstrap.&lt;/li&gt;\n&lt;li&gt;Demo &amp;ndash\; creating a project\, adding 
 dependencies\, and inspecting the generated lock file.&lt;/li&gt;\n&lt;li&gt;Running t
 asks &amp;ndash\; using pixi run to execute scripts\, tests\, and CI commands 
 defined in the TOML.&lt;/li&gt;\n&lt;li&gt;Managing multiple environments &amp;ndash\; swi
 tching between dev\, test\, and production stacks with a single configurat
 ion.&lt;/li&gt;\n&lt;/ul&gt;\n&lt;p&gt;&amp;nbsp\;&lt;/p&gt;\n&lt;p&gt;The goal is to show how Pixi streamli
 nes setup\, reproducibility\, and automation from a local workstation all 
 the way through CI/CD pipelines.&lt;/p&gt;
END:VEVENT
END:VCALENDAR

