[issue7989] Transition time/datetime C modules to Python

2010-06-08 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: Brett Cannon wrote: > > Brett Cannon added the comment: > > So I see a couple of objections here to the idea that I will try to address. > > First is MAL's thinking that this will undo any C code, which it won't. The > idea is that stdlib modules that d

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Brett, Thanks for your explanation. It looks like I misunderstood the proposal. I though the idea was to have some methods of e.g. date type implemented in python and some in C. What you propose is much simpler. Effectively, your proposal is "let's

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread anatoly techtonik
anatoly techtonik added the comment: It would be nice to see the transition accompanied by some tutorial that could be used as an example for other similar tasks. -- nosy: +techtonik ___ Python tracker ___

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Brett Cannon
Brett Cannon added the comment: So I see a couple of objections here to the idea that I will try to address. First is MAL's thinking that this will undo any C code, which it won't. The idea is that stdlib modules that do not inherently rely on other C code (e.g. sqlite3 does not fall undernea

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Also, my opposition is only to splitting datetime. While I am not against splitting the time module, I believe it should be phased out eventually and posix compatibility portion folded into posix module. --

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: Brett Cannon wrote in a comment (msg106498) on another issue: """ The stated long-term goal of the stdlib is to minimize the C extension modules to only those that have to be written in C (modules can still have performance enhancing extension back-ends

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Brian Curtin
Brian Curtin added the comment: It seems like this might not be worth it or a good idea, and I have no strong feeling for this being done. Feel free to close/reject this one. -- ___ Python tracker

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Alexander Belopolsky
Changes by Alexander Belopolsky : -- versions: -Python 2.7 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: For the datetime module there are also a few more subtle issues that would make it difficult to make a hybrid C/Python implementation. The problem is that unlike the time module where most of the functionality is implemented in module level functions,

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Daniel Urban
Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.or

[issue7989] Transition time/datetime C modules to Python

2010-06-07 Thread Marc-Andre Lemburg
Marc-Andre Lemburg added the comment: Alexander Belopolsky wrote: > > Alexander Belopolsky added the comment: > > As far as I remember, the datetime module started as a pure python module and > was reimplemented in C around year 2003 or so. One of the important > additions at that time was

[issue7989] Transition time/datetime C modules to Python

2010-06-05 Thread Alexander Belopolsky
Alexander Belopolsky added the comment: As far as I remember, the datetime module started as a pure python module and was reimplemented in C around year 2003 or so. One of the important additions at that time was the C API to datetime functionality. I am afraid that with the _timemodule.c/t

[issue7989] Transition time/datetime C modules to Python

2010-02-22 Thread Brian Curtin
Brian Curtin added the comment: Correct, your wording is better than mine. I'll ask around and see where that datetime module may be and what it's state is. -- ___ Python tracker _

[issue7989] Transition time/datetime C modules to Python

2010-02-22 Thread R. David Murray
R. David Murray added the comment: By 'convert', I believe you mean 'create a python implementation of'. That is, there's no reason to drop any c code, just to create parallel python versions when possible. Also note that one of the alternate implementations (IronPython I think) has an impl

[issue7989] Transition time/datetime C modules to Python

2010-02-22 Thread Brian Curtin
New submission from Brian Curtin : After discussion on numerous issues, python-dev, and here at the PyCon sprints, it seems to be a good idea to move timemodule.c to _timemodule.c and convert as much as possible into pure Python. The same change seems good for datetime.c as well. -- c