[ python-Bugs-990569 ] printing date causes crash

[SourceForge.net]

Bugs item #990569, was opened at 2004-07-14 09:53
Message generated for change (Comment added) made by mhammond
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=990569&group_id=5470

Category: Python Interpreter Core
Group: Python 2.3
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Justin (jmuir)
Assigned to: Nobody/Anonymous (nobody)
Summary: printing date causes crash

Initial Comment:
Hi,

I'm using Python 2.3.4 + PythonWin 1.63 to manipulate
some Access databases. It appears that a default date
set in the database is causing python to crash when
attempting to print it. All records which have a
different(relatively current - 2000 onwards) date print
fine. The default date is set to 31-Dec-1955. There's
nothing particular about the date that I cannot change
it, just thought you should know that date was causing
a problem.

C:\Work>python
Python 2.3.4 (#53, May 25 2004, 21:17:02) [MSC v.1200
32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for
more information.
>>>


I've attached the error file generated by windows.


Justin

----------------------------------------------------------------------

>Comment By: Mark Hammond (mhammond)
Date: 2004-07-19 23:07

Message:
Logged In: YES 
user_id=14198

This should be a bug in the pywin32 project, not Python
itself - however, this has been fixed in recent builds - the
latest is build 202.

----------------------------------------------------------------------

Comment By: Justin (jmuir)
Date: 2004-07-17 02:24

Message:
Logged In: YES 
user_id=1083084

Mornin'!


Well, I'm thinking that it may be simpler to send you a copy
of the table/db and the offending code. Do you have access
to a M$ platform?

Justin

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2004-07-16 10:41

Message:
Logged In: YES 
user_id=33168

It doesn't help me, but I'm not a windows guy anyways. :-)

Is there an extention module for Access?  It seems like the
problem may be there or perhaps it's general to windows. 
You could try contacting whoever distributes the module. 
Hopefully someone else can help.  If you can give me a test
example that demonstrates the problem in the interpreter, I
can try to look into this. 

----------------------------------------------------------------------

Comment By: Justin (jmuir)
Date: 2004-07-16 10:14

Message:
Logged In: YES 
user_id=1083084

Doh! 

Here's how I reproduced the bug:

1. Started Access 
2. Changed a single date field to 31-Dec-55.
3. Close Access
4. Ran python script to print records...and presto! Crash.


As I look at that date I can't help wondering if it's being
passed back to Python as 2055?


Justin

----------------------------------------------------------------------

Comment By: Justin (jmuir)
Date: 2004-07-16 09:58

Message:
Logged In: YES 
user_id=1083084

Ok, I've attached the file now. 

Hope it helps!


Justin

----------------------------------------------------------------------

Comment By: Justin (jmuir)
Date: 2004-07-16 09:20

Message:
Logged In: YES 
user_id=1083084

Hello,

Damn, I've already changed the default date in my db...hang
on, I'll do it again and send the file....

btw - I tried to reproduce the error in the interpreter by
instantiating a date and a datetime object with that date.
No crash. I wonder if it's something to do with what Access
is passing to Python?

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2004-07-16 08:23

Message:
Logged In: YES 
user_id=33168

Can you reproduce the problem from the python interpreter
w/o the database?

----------------------------------------------------------------------

Comment By: Neal Norwitz (nnorwitz)
Date: 2004-07-16 08:22

Message:
Logged In: YES 
user_id=33168

There's no uploaded file!  You have to check the
checkbox labeled "Check to Upload & Attach File"
when you upload a file.

Please try again.

(This is a SourceForge annoyance that we can do
nothing about. :-( )

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=990569&group_id=5470