This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vinay.sajip
Recipients tphh, vinay.sajip, xtreak
Date 2018-11-05.19:45:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I agree that it's inconsistent, but quite a bit of setting up is done when punctuation_chars is provided, as per the link in msg329312. One could convert the attribute to a property and have a setter that does the equivalent set up, but some of the setup is one-time (removing things from wordchars, etc.), and would require additional work to handle the case where the property is reassigned multiple times. I have no problem updating the documentation to indicate in a note that it must be provided in the constructor and not later, but apart from the fact that it's inconsistent, is there a use case for supporting setting it later? That would mean setting it up so that you could set it several times, unset it, etc.
Date User Action Args
2018-11-05 19:45:07vinay.sajipsetrecipients: + vinay.sajip, xtreak, tphh
2018-11-05 19:45:07vinay.sajipsetmessageid: <>
2018-11-05 19:45:07vinay.sajiplinkissue35168 messages
2018-11-05 19:45:06vinay.sajipcreate