You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee=Noneclosed_at=<Date2019-09-05.13:37:57.279>created_at=<Date2019-03-23.16:11:49.750>labels= ['OS-mac', 'library', '3.9']
title='plistlib old API should be removed'updated_at=<Date2019-09-05.13:37:57.279>user='https://github.com/Bigfootjon'
Per the documentation and in-line code warnings, the old API for plistlib was deprecated in version 3.4. My understanding is that deprecated functionality is to be removed in the next major version, so this code is long overdue for removal.
It was preserved for compatibility with Python 2.7. From PEP-4:
"In order to facilitate writing code that works in both Python 2 & 3 simultaneously, any module that exists in both Python 3.5 and Python 2.7 will not be removed from the standard library until Python 2.7 is no longer supported as specified by PEP-373."
3.9 will be the first Python 3 release after the EOL of 2.7.
Ah, I misinterpreted PEP-4. I thought it only applied to modules as a whole (e.g. plistlib) rather than individual functionality within that module. I'll close my PR and wait until 3.9 is accepting patches
Yes, this is mainly about modules, but in general we try to be more careful with removing features that do not have alternatives in 2.7. In this particular case, the benefit from removing the deprecated functions in 3.8 instead of 3.9 is small, but this will make harder writing 2+3 compatible code.
In any case this is on to the module maintainer, Ronald.