mirrors/apparmor
1
0
Fork 0
mirror of https://gitlab.com/apparmor/apparmor.git synced 2025-03-04 08:24:42 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update MeetingAgenda

Ryan Lee 2024-12-04 20:07:05 +00:00
parent 21b58fdde1
commit 1af193d8ec
1 changed files with 6 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
MeetingAgenda.md

@ -38,10 +38,13 @@ announcements will be sent out to the apparmor mailing list
- rlee287: Review of a draft CONTRIBUTING.md (fill in a MR link before the actual meeting)
- Documents versions of GCC, Python etc.
- Profile testing instruction stuff (written as part of a Canonical effort to have more AppArmor profiles, but also stuff that we'd want other profile contributors to observe)
- rlee287: Reconsidering Python 3.5 as the baseline for the utils (specifically)
- rlee287: AppArmor utils currently using features beyond Python 3.5
- AppArmor Python utils contain Python f-strings (3.6) and `datetime.datetime.fromisoformat` (3.7) and possibly other things too
- f-strings would be easy enough to remove, but `fromisoformat` would need a polyfill
- How do we want to approach complications like a potential need to polyfill newer Python library features?
- If we decide to polyfill we could perhaps polyfill the required cgitb functionality forward for Python 3.13
- Alternative to polyfilling: reconsidering Python 3.5 as the baseline for the utils (specifically)
- I'm in favor of sticking to Python 3.5 and not splitting the minimum version requirements (or at most Python 3.6 of OpenSUSE Leap, if we must split)
- AppArmor Python utils contain Python f-strings (3.6) and `datetime.datetime.fromisoformat` (3.7)
- f-strings would be easy enough to remove, but `fromisoformat` would need a polyfill, which I'd want to talk out before committing to the effort of copying it from upstream Python
### [IRC Meeting, 18:00 UTC, Tue Nov 12, 2024](IRC_meeting_2024-11-12)