Re: postgresql range types v2

2013-01-17 Thread Marco Paolini
On Thursday, January 17, 2013, Simon Litchfield wrote: > Marco, this is great. Thanks, did you give it a try? > > I wonder if it would be possible to add range fields without modifying > django? > Very difficult, there are many small changes scattered around the core django ORM and driver code

Re: postgresql range types v2

2013-01-17 Thread Marco Paolini
On Thursday, January 17, 2013, Simon Litchfield wrote: > Also, did you see psycopg2.extras.DateTimeRange? > > No, I missed that one ! Thanks I 'll see if it can be used somehow, but since the range types have to be used by the core django code, I doubt they can be imported from a third party libr

Reminder: pending Oracle fixes and issues

2013-01-17 Thread Shai Berger
Hi Django devs, and in particular Oracle users, This is to remind you of fixes I proposed for the Oracle backend, which were mostly discussed and accepted, but seem not to have made it into the codebase yet. I am referring to: - PR #393[0] - Includes two separate issues -- of which one has been

new contributor

2013-01-17 Thread Michael Lauria
Hi, I'd like to get involved, but I have no idea where to start. Could anyone suggest something? Thanks in advance. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/d

Re: Reminder: pending Oracle fixes and issues

2013-01-17 Thread Jani Tiainen
17.1.2013 15:50, Shai Berger kirjoitti: Hi Django devs, and in particular Oracle users, This is to remind you of fixes I proposed for the Oracle backend, which were mostly discussed and accepted, but seem not to have made it into the codebase yet. I am referring to: What comes to your fix for

Re: Reminder: pending Oracle fixes and issues

2013-01-17 Thread Anssi Kääriäinen
On 17 tammi, 15:50, Shai Berger wrote: > Besides these two, I would like to continue the discussion on PR #402[3]; it > suggests adding a flag to Oracle's DATABASE_OPTIONS, to control how it returns > explicit expressions from raw sql ("select 1.5 from ..."). The current backend > (also after incl

Re: new contributor

2013-01-17 Thread Aymeric Augustin
Le 17 janv. 2013 à 16:00, Michael Lauria a écrit : > Hi, I'd like to get involved, but I have no idea where to start. Could anyone > suggest something? Thanks in advance. Hi Michael, The documentations contains a wealth of information about getting involved: https://docs.djangoproject.com/en/d

Re: new contributor

2013-01-17 Thread donarb
On Jan 17, 7:00 am, Michael Lauria wrote: > Hi, I'd like to get involved, but I have no idea where to start. Could > anyone suggest something? Thanks in advance. https://code.djangoproject.com/#Gettinginvolved -- You received this message because you are subscribed to the Google Groups "Django

Re: new contributor

2013-01-17 Thread CJ Goldsmith
There are some great videos that reference this situation if you search for the djangocon 2012 videos -CJ- Sent from my iPhone On Jan 17, 2013, at 7:00 AM, Michael Lauria wrote: > Hi, I'd like to get involved, but I have no idea where to start. Could anyone > suggest something? Thanks in adv

Re: postgresql range types v2

2013-01-17 Thread Russell Keith-Magee
On Mon, Dec 31, 2012 at 5:56 PM, Marco Paolini wrote: > Hi all, > > sorry for the noise, forget my previous mail as it was pointing to the > wrong commit, > here's the good one: > > https://github.com/mpaolini/**django/commit/** > b754abdeab204949510500ccb1b845**b7ad143542

Re: Github tags

2013-01-17 Thread Yo-Yo Ma
Sorry to be a pest, but will you guys end up adding a Git tag for RC-1? On Sunday, October 28, 2012 10:38:00 PM UTC-4, Matt Austin wrote: > > Hi, > > Would it be possible to get tags for 1.3.3, 1.3.4, 1.4.2, and 1.5 > alpha tagged on the github repository? The tagging seems to have > fallen beh