This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: printing date causes crash
Type: Stage:
Components: Interpreter Core Versions: Python 2.3
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: Nosy List: jmuir, mhammond, nnorwitz
Priority: normal Keywords:

Created on 2004-07-13 23:53 by jmuir, last changed 2022-04-11 14:56 by admin. This issue is now closed.

Files
File name Uploaded Description Edit
appcompat.txt jmuir, 2004-07-15 23:49
Messages (9)
msg21559 - (view) Author: Justin (jmuir) Date: 2004-07-13 23:53
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
msg21560 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2004-07-15 22:22
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. :-( )
msg21561 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2004-07-15 22:23
Logged In: YES 
user_id=33168

Can you reproduce the problem from the python interpreter
w/o the database?
msg21562 - (view) Author: Justin (jmuir) Date: 2004-07-15 23:20
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?
msg21563 - (view) Author: Justin (jmuir) Date: 2004-07-15 23:58
Logged In: YES 
user_id=1083084

Ok, I've attached the file now. 

Hope it helps!


Justin
msg21564 - (view) Author: Justin (jmuir) Date: 2004-07-16 00:14
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
msg21565 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2004-07-16 00:41
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. 
msg21566 - (view) Author: Justin (jmuir) Date: 2004-07-16 16:24
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
msg21567 - (view) Author: Mark Hammond (mhammond) * (Python committer) Date: 2004-07-19 13:07
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.
History
Date User Action Args
2022-04-11 14:56:05adminsetgithub: 40555
2004-07-13 23:53:24jmuircreate