Rather using Monday const from built-in calendar.py#791
Rather using Monday const from built-in calendar.py#791bletham merged 1 commit intofacebook:masterfrom
Conversation
Latest version of holidays (0.9.9) changed the name of its MONDAY const to MON. Rather using the MONDAY const from the same library as the object that it is being used with.
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed. If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks! |
|
Hi! |
|
Hey @ivonnics , @louisguitton suggested a work around in the issue that he opened. |
|
This is great, thanks so much for the fix. |
|
An especially good fix because it works with both old and new versions of holidays. |
|
|
|
heh, well all is well that ends well :-) |
Latest version of
python-holidays(0.9.9) changed the name of itsMONDAYconst toMON. Rather using theMONDAYconst from the same library as the object that it is being used with (calendarmodule).Also, given this constant is 19 years old (!), I suspect it might not change in the near future.