Changeset 779


Ignore:
Timestamp:
Jan 21, 2005, 4:35:22 PM (20 years ago)
Author:
ole
Message:

Cleanup

File:
1 edited

Legend:

Unmodified
Added
Removed

  • inundation/ga/storm_surge/pyvolution/wiki/issues.txt

    r711 r779  
    4242Who: DSG
    4343 
    44 Issue: Exceptions thrown by Python functions called from C don't get caughts
    45 Background: Have a look at gravity in shallow_water. It calls a C function, gradient, which may throw an exception if arguments are scalars.
    46 However, it doesn't get caught becuase gravity itself is called from within C
    47 Importance: Low
    48 Suggested Action: Have a look at the calling convention from C (David Beasley)
    49 Status: Unresolved
    5044
    5145
    … …  
    144138
    145139
     140
    146141Issue: Checkpointing - needs to always back one timestep up in
    147142       case output wasn't written
    … …  
    162157Status: Was done when whole things was refactored in April 2004 by OMN
    163158
    164 ##Here is a test line
     159
     160Issue: Exceptions thrown by Python functions called from C don't get caughts
     161Background: Have a look at gravity in shallow_water. It calls a C function, gradient, which may throw an exception if arguments are scalars.
     162However, it doesn't get caught becuase gravity itself is called from within C
     163Importance: Low
     164Suggested Action: Have a look at the calling convention from C (David Beasley)
     165Status: Unresolved - but no longer relevant as we don't call Python from C
     166
Note: See TracChangeset for help on using the changeset viewer.