[Casa-framework] Table lock under python

[Lindsey Davis]

Hi,

I have forgotten all the issues associated with table locking, but I do
remember that there were inconsistencies across the various tools. Some
tools exposed lock / unlock methods to the user and others handled this
internally. To the extent this matters now, it would be nice to harmonize
interfaces across tools.

I also remember that there were problems with table cacheing / statics
under the old protopipeline which probably no longer matter ?

At any rate these kinds of problems do not seem to be troubling the
heuristics group anymore.

                                                       Lindsey


On Wed, 27 Sep 2006, Ger.VanDiepen at csiro.au wrote:

> Yes, that'll be the case. In Python everything is in one process, so
> they share all locks. Of course, you do not need to quit python. You can
> unlock a table.
>
> Ger
>
> -----Original Message-----
> From: casa-framework-bounces at donar.cv.nrao.edu
> [mailto:casa-framework-bounces at donar.cv.nrao.edu] On Behalf Of Kumar
> Golap
> Sent: Wednesday, 27 September 2006 8:13 AM
> To: casa-framework at nrao.edu; Ger van Diepen
> Subject: [Casa-framework] Table lock under python
>
> I've noticed an interesting locking issue... Maybe because now that
> the python and the table or ms tool or any other too have the same
> process id ...the lock on tables seems to hold even after quit the
> tool.  So if i access the same table via the glish table tool say it
> waits on the lock till I quit python.
>
> Kumar
> _______________________________________________
> Casa-framework mailing list
> Casa-framework at donar.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/casa-framework
>
> _______________________________________________
> Casa-framework mailing list
> Casa-framework at donar.cv.nrao.edu
> http://listmgr.cv.nrao.edu/mailman/listinfo/casa-framework
>