Missed 1.3 feature deadline. Will it become core?

Semprini commented 13 years ago

Just wondering if anyone knows if it's lethargy or strategy that caused this to be overlooked for 1.3...

jezdez commented 13 years ago

Just wondering if anyone knows if it's lethargy or strategy that caused this ticket to sound like a message from a troll...

johnpaulett commented 13 years ago

I have not pushed the original issue from my side, as this side-project is fulfilling my needs. I am happy to help try to get this code applied to the Django trunk if you want to take the lead on pinging django-developers.

johnpaulett commented 13 years ago

After talking to a few Django core developers at PyCon, it sounds keeping as a standalone, reusable app is still preferable. A few reasons

Many databases lack native support for an interval type. PostgreSQL does, but others do not. Storing as a bigint works, but is not a perfect mapping to the SQL standard
By being a standalone app, we are able to quickly innovate, instead of locking ourselves into a certain API or implementation.

I am more than happy to help with an effort to resubmit this application as a patch to Django if there is community interested, however it sounds like most users prefer it as a reusable application.

johnpaulett / django-durationfield

Missed 1.3 feature deadline. Will it become core? #3