Re: BC date getting misinterpreted?

To be a bit more useful ( :) ), if you really need to deal with proleptic Gregorian dates that far back, you might consider reading it out as a string and using Astropy for date arithmetic:

http://www.astropy.org

> On Mar 26, 2018, at 16:15, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
> In both 2.7 and 3.6, datetime.MINYEAR is 1, so I'm a bit surprised this ever worked.
>
>> On Mar 26, 2018, at 16:11, Joe Abbate <jma(at)freedomcircle(dot)com> wrote:
>>
>> The test case is fairly simple:
>>
>> curs.execute("SELECT '044-03-15 BC'::date")
>> rows = curs.fetchall()
>>
>> This results in:
>>
>> ValueError: year -43 is out of range
>>
>> [This is Python 3.6, in 2.7, the value is missing]
>>
>> This was working since last October, but the error started happening around the Ides of March (my actual dates are different, but I changed the example to fit :-)
>>
>> Tested against 9.3 thru 10.
>>
>> Joe
>>
>
> --
> -- Christophe Pettus
> xof(at)thebuild(dot)com
>

--
-- Christophe Pettus
xof(at)thebuild(dot)com