[issue16058] ConfigParser no longer deepcopy compatible in 2.7

2020-04-26 Thread Zachary Ware
Zachary Ware added the comment: With 2.7 now EOL, I'm closing the issue. -- nosy: +zach.ware resolution: fixed -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___

[issue16058] ConfigParser no longer deepcopy compatible in 2.7

2016-12-21 Thread Łukasz Langa
Łukasz Langa added the comment: Solved in 3.2+ by making it compatible with the Mapping protocol. So while you can't do deepcopy(), you can `parser2.read_dict(parser1)`. -- dependencies: -Regex objects became uncopyable in 2.5 resolution: -> fixed

[issue16058] ConfigParser no longer deepcopy compatible in 2.7

2016-12-13 Thread Serhiy Storchaka
Changes by Serhiy Storchaka : -- dependencies: +Regex objects became uncopyable in 2.5 ___ Python tracker ___ ___ Python-bugs-list mai

[issue16058] ConfigParser no longer deepcopy compatible in 2.7

2016-12-13 Thread Camilla Montonen
Changes by Camilla Montonen : -- nosy: +Winterflower ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://ma

[issue16058] ConfigParser no longer deepcopy compatible in 2.7

2012-10-05 Thread Andrew Svetlov
Andrew Svetlov added the comment: ConfigParser is not intended to be deep copy-able, at least documentation says nothing about it. -- nosy: +asvetlov, lukasz.langa ___ Python tracker __

[issue16058] ConfigParser no longer deepcopy compatible in 2.7

2012-09-26 Thread Robert Collins
New submission from Robert Collins: In 2.6 deepcopy(ConfigParser) worked, in 2.7 it doesn't due to the _optcre variable which is a compiled regex pattern. -- components: Library (Lib) messages: 171364 nosy: rbcollins priority: normal severity: normal status: open title: ConfigParser no