veyepar: The Perfect Python Project

Author(s):	Glyph
Location	Reis River Ranch
Date	jun Sat 29	Days Raw Files
Start	10:25	First Raw Start	09:51
Duration	00:25:00	Offset	0:33:46
End	10:50	Last Raw End	11:21
Chapters	00:00 0:15:22
Total cuts_time	26 min.

https://pretalx.northbaypython.org/nbpy-2024/talk/RYQVSH
raw-playlist raw-mp4-playlist encoded-files-playlist host archive mp4 svg png

assets release.pdf The_Perfect_Python_Project.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

Do you want to create a Python project?

Do you want it to be good?

There have been lots of talks and posts and books about how to improve your project by adopting this or that tool or technology, by adopting a best practice.  We all want to improve.  We all want our code to be more correct. Faster. Friendlier. Easier to use. Better documented. Better tested. To have better coverage. Easier to contribute to. Easier to work on. More welcoming as a community. More repeatable. Less flaky. More secure. More sustainable. Easier to install. Easier to deploy. Easier to manage. Easier to discover. Easier to discuss, to report issues, to investigate issues, to triage issues.

What if we did all the things though?  How could we make our project perfect?

In this talk, I will explore a comprehensive review of all of the best practices available to Python projects; a few specific to open source, but most applicable to just about anything written in Python.  In addition to learning about many, many best practices, their importance, and the tools available to facilitate them, I will also propose some solutions to the overwhelming sense of existential dread that one might feel when confronted with all of them at once.

Comment:

production notes

barn/2024-06-29/09_51_14.ts Apply: 09:52:56 - 10:19:44 ( 00:26:48 ) S: 09:51:14 - E: 10:21:13 D: 00:29:59 (Start: 102.0) (End: 1710.0) show more...

vlc ~/Videos/veyepar/nbpy/NBPy2024/dv/barn/barn/2024-06-29/09_51_14.ts :start-time=0102.0 --audio-desync=0

	Raw File	Cut List
	09:51:14		seconds: 102.0 Wall: 09:52:56
Duration	00:29:59
	10:21:13		seconds: 1710.0 Wall: 10:19:44
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

barn/2024-06-29/10_21_14.ts Apply: 10:35:20 - 10:35:52 ( 00:00:32 ) S: 10:21:14 - E: 10:51:14 D: 00:30:00 (Start: 846.0) (End: 878.0) show more...

vlc ~/Videos/veyepar/nbpy/NBPy2024/dv/barn/barn/2024-06-29/10_21_14.ts :start-time=0846.0 --audio-desync=0

	Raw File	Cut List
	10:21:14		seconds: 846.0 Wall: 10:35:20
Duration	00:30:00
	10:51:14		seconds: 878.0 Wall: 10:35:52
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete

barn/2024-06-29/10_51_14.ts Apply: 11:02:38 - 11:03:35 ( 00:00:57 ) S: 10:51:14 - E: 11:21:13 D: 00:29:59 (Start: 684.0) (End: 741.0) show more...

vlc ~/Videos/veyepar/nbpy/NBPy2024/dv/barn/barn/2024-06-29/10_51_14.ts :start-time=0684.0 --audio-desync=0

	Raw File	Cut List
	10:51:14		seconds: 684.0 Wall: 11:02:38
Duration	00:29:59
	11:21:13		seconds: 741.0 Wall: 11:03:35
Comments:
mp4 mp4.m3u	dv.m3u	Split: Sequence:: delete