I've taken a run through the current Python Policy to see where I think it needs to be updated for Stretch. The updates largely fall into four categories: 1. Update old examples 2. Clean up old policy test that no longer applies 3. Simplify things due to there only being one python version 4. Make the text better match current practice I've sent this twice now and the list didn't like it for different reasons, so I've posted [1] the diff I've come up with so far in rfcdiff format (because I think it's easier to read that unified diffs for this kind of thing). This is just my opinion on stuff I found. I'm interested in feedback on how these changes look and what else ought to be considered (no: rewrite the whole thing is not useful feedback unless you provide the text). While I don't have any specific near-term deadlines for this, at least one of the proposals (killing off python:Provides) will take a little while to accomplish, so I would like to get consensus on what's reasonable sooner rather than later. Scott K [1] http://kitterman.com/debian/python-policy.new-from-old.diff.html
Attachment:
signature.asc
Description: This is a digitally signed message part.