Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'calendar' module is crummy and should be removed #49239

Closed
dotz mannequin opened this issue Jan 18, 2009 · 4 comments
Closed

'calendar' module is crummy and should be removed #49239

dotz mannequin opened this issue Jan 18, 2009 · 4 comments
Labels
type-feature A feature request or enhancement

Comments

@dotz
Copy link
Mannequin

dotz mannequin commented Jan 18, 2009

BPO 4989
Nosy @smontanaro, @brettcannon, @benjaminp

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

GitHub fields:

assignee = None
closed_at = <Date 2009-01-18.19:47:10.055>
created_at = <Date 2009-01-18.19:36:51.519>
labels = ['type-feature']
title = "'calendar' module is crummy and should be removed"
updated_at = <Date 2009-01-19.00:58:05.117>
user = 'https://bugs.python.org/dotz'

bugs.python.org fields:

activity = <Date 2009-01-19.00:58:05.117>
actor = 'skip.montanaro'
assignee = 'none'
closed = True
closed_date = <Date 2009-01-18.19:47:10.055>
closer = 'benjamin.peterson'
components = ['None']
creation = <Date 2009-01-18.19:36:51.519>
creator = 'dotz'
dependencies = []
files = []
hgrepos = []
issue_num = 4989
keywords = []
message_count = 4.0
messages = ['80115', '80118', '80133', '80140']
nosy_count = 4.0
nosy_names = ['skip.montanaro', 'brett.cannon', 'benjamin.peterson', 'dotz']
pr_nums = []
priority = 'normal'
resolution = 'rejected'
stage = None
status = 'closed'
superseder = None
type = 'enhancement'
url = 'https://bugs.python.org/issue4989'
versions = ['Python 2.6', 'Python 3.0', 'Python 3.1', 'Python 2.7']

@dotz
Copy link
Mannequin Author

dotz mannequin commented Jan 18, 2009

I was looking for some library to handle calendar events. Something PIM-
style, something useful, that could check if, for example, 2 weekly
repeated events that start on Monday morning and last until December
conflict with each other.

Then I found 'calendar' module in the standard library.

My question: how this thing ever made it to the standard library?

Maybe it was useful back in the days, if somebody could not get BSD or
GNU sources for cal(1) . Nowadays, even if it is able to print HTML
calendars, lets face it - who will use that functionality? You can
easily find HTML calendars with a lot of JavaScript support, that can be
customised in a thousands of ways.

I suggest we delete this module completly.

@dotz dotz mannequin added the type-feature A feature request or enhancement label Jan 18, 2009
@benjaminp
Copy link
Contributor

We cannot just remove modules because of backwards compatibility. Feel
free to submit patches for improvements you would like to see in the module.

@brettcannon
Copy link
Member

The other option is to propose its removal on python-dev, get support,
and then submit patches for the module's deprecation.

@smontanaro
Copy link
Contributor

Look at the oldest checkin comment for a line still in the module:

r2166 | guido | 1990-10-13 14:23:40 -0500 (Sat, 13 Oct 1990) | 2 lines

Initial revision

In short, it's been there for a long, long time. Long before PEPs.
Long before Tkinter. Long before cmath. Probably long before any code
which would satisfy your needs was written. Of all the checkin comments
for lines still in the current trunk, calendar.py has code which is
within a few revisions of the earliest code in the repository.

Skip

@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type-feature A feature request or enhancement
Projects
None yet
Development

No branches or pull requests

3 participants