veyepar: Inside the Cheeseshop: How Python Packaging Works

Author(s):	Dustin Ingram
Location	Barbie Tootle
Date	jul Sat 28	Days Raw Files
Start	15:00	First Raw Start	14:40
Duration	0:30:0	Offset	0:19:17
End	15:30	Last Raw End	15:40
Chapters	00:00 0:11:11
Total cuts_time	32 min.

https://pyohio.org/2018/schedule/presentation/46/
raw-playlist raw-mp4-playlist encoded-files-playlist host archive tweet mp4 svg png

assets release.pdf Inside_the_Cheeseshop_How_Python_Packaging_Works.json
logs
Admin: episode episode list cut list raw files day marks day marks day image_files

State:

Locked:

clear this to unlock

Locked by:

user/process that locked.

Start:

initially scheduled time from master, adjusted to match reality

Duration:

length in hh:mm:ss

Name:

Video Title (shows in video search results)

Emails:

email(s) of the presenter(s)

Released:

has someone authorised pubication

Normalise:

Channelcopy:

m=mono, 01=copy left to right, 10=right to left, 00=ignore.

Thumbnail:

filename.png

Description:

markdown

Questions and confusion about the Python packaging ecosystem abound. What is this `setup.py` file? What's the difference between wheels and eggs? Do I use setuptools or distutils? Why should I use twine? Do I put my projects dependencies in a `requirements.txt` or in `setup.py`? How do I just get my module up on PyPI? Wait, what is Warehouse?

This talk will identify the key tools one might encounter when trying to distribute Python software, what they are used for, why they exist, and their history (including where their weird names come from). In addition, we'll see how they all work together, what it takes to make them work, and what the future has in store for Python packaging.

This talk is for any Pythonista that has been confused by Python Packaging (read: everyone).

This talk requires that the audience has just the slightest familiarity with how Python Packaging works -- that you need to upload your source code, that there are a few popular and familiar tools, and that they are all a little confusing. Attendees do not need to be publishers of Python Packages but likely will be people interested in publishing someday.

After watching this talk, attendees should have a significant amount of their confusion about the Python packaging ecosystem resolved, and should be able to make informed, reasonable decisions when they want to publish a package (without having to be told step by step instructions, or given extremely opinionated advice).

Comment:

production notes