JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for SYNERBI-DEVEL Archives


SYNERBI-DEVEL Archives

SYNERBI-DEVEL Archives


SYNERBI-DEVEL@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

SYNERBI-DEVEL Home

SYNERBI-DEVEL Home

SYNERBI-DEVEL  December 2016

SYNERBI-DEVEL December 2016

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: spyder second run problem

From:

Evgueni Ovtchinnikov <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Mon, 12 Dec 2016 11:54:25 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (38 lines)

Forgot to explain earlier:

We have problems on Spyder ONLY when we make out test scripts 'proper' scripts, i.e. if main(): is replaced with try:, and try: main() (just before except error as err:) is removed (so you need to do this if you want to see for yourself error messages on second run in Spyder). The reason for introducing main() was exactly this second run problem. However, if our scrips are essentially functions, all data disappears after script finishes, which is not what one expects from a script. This is why we started seeking help with this issue rather than continue 'papering over the crack'.

By the way, no error messages are issued if a 'proper' script is executed twice in Python command shell. So, this appears to be a Spyder-specific problem rather than a bug in our interface.

On the bright side: problem disappears if one selects 'Execute in a new dedicated Python console' in Spyder Run Settings - not a perfect solution, but sill a better option than 'function-scripts' do you think?

-----Original Message-----
From: CCP-PETMR Developers list [mailto:[log in to unmask]] On Behalf Of Evgueni Ovtchinnikov
Sent: 09 December 2016 16:59
To: [log in to unmask]
Subject: Re: spyder second run problem

Well, actually, spyder reloads them, and pyiutil is loaded in pGadgetron.py, which calls pyiutil.deleteObject() methods.

From: Casper da Costa-Luis [[log in to unmask]]
Sent: Friday, December 09, 2016 4:34 PM
To: Ovtchinnikov, Evgueni (STFC,RAL,SC)
Cc: [log in to unmask]
Subject: Re: spyder second run problem

Why do we need to "reload modules?" Perhaps if required reload pGadgetron before pyiutil?

On 9 December 2016 at 15:50, Evgueni Ovtchinnikov <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Hi All,

When we run any of our scripts second time in spyder, we get error messages of the kind

runfile('/cs/research/external/home/eovtchin/devel/xGadgetron/examples/coil_sensitivity_maps.py', wdir='/cs/research/external/home/eovtchin/devel/xGadgetron/examples')
Reloaded modules: ismrmrdtools, pyiutil, pGadgetron, six, _pyiutil, _pygadgetron, ismrmrdtools.coils, pygadgetron Exception AttributeError: "'NoneType' object has no attribute 'deleteObject'" in <bound method AcquisitionData.__del__ of <pGadgetron.AcquisitionData instance at 0x23d3e18>> ignored

for every object that calls pyiutil.deleteObject() from __del__ (the above message is for an AcquisitionData object).

The error message suggests that by the time __del__ is called, module pyiutil has already been destroyed.

Any ideass how to get rid of these error messages?

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
November 2015


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager