Error executing import scripts...

26 views
Skip to first unread message

Tim de Wit

unread,
Jan 9, 2018, 2:34:28 AM1/9/18
to OpenREM
After updating to the development version, i get the following errors in my conquest logging:

openrem-rdsr: /var/lib/conquest-dicom-server/incoming/1.3.12.2.1107.5.1.4.75508.30000018010117412872200000200.dcm
Traceback (most recent call last):
  File "/usr/local/bin/openrem_rdsr.py", line 23, in <module>
    rdsr(filename)
TypeError: 'module' object is not callable
openrem-rdsr: /var/lib/conquest-dicom-server/incoming/1.3.12.2.1107.5.1.4.95841.30000017122609185966600007384.dcm
Traceback (most recent call last):
  File "/usr/local/bin/openrem_dx.py", line 23, in <module>
    dx(filename)
TypeError: 'module' object is not callable

I get this for all import scripts. Any ideas?

Ed McDonagh

unread,
Jan 9, 2018, 3:06:50 AM1/9/18
to Tim de Wit, OpenREM
Hi Tim

I assume that is related to https://bitbucket.org/openrem/openrem/issues/567/celery-extractor-tasks-imported-with-two - though I thought it had been tested for this?

It sounds like the imports in the __init__.py script aren't being used so the module is being called rather than the functions in the module.

I'll take a look. Might be easiest to modify the scripts.

Ed


--
You received this message because you are subscribed to the Google Groups "OpenREM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrem+unsubscribe@googlegroups.com.
To post to this group, send email to ope...@googlegroups.com.
Visit this group at https://groups.google.com/group/openrem.
For more options, visit https://groups.google.com/d/optout.

Tim de Wit

unread,
Jan 9, 2018, 3:37:43 AM1/9/18
to OpenREM
Very likely indeed... I checked whether the errors in the celery logfile were solved but did not actually check the script output :(


On Tuesday, January 9, 2018 at 9:06:50 AM UTC+1, Ed McDonagh wrote:
Hi Tim

I assume that is related to https://bitbucket.org/openrem/openrem/issues/567/celery-extractor-tasks-imported-with-two - though I thought it had been tested for this?

It sounds like the imports in the __init__.py script aren't being used so the module is being called rather than the functions in the module.

I'll take a look. Might be easiest to modify the scripts.

Ed

On 9 Jan 2018 07:34, "Tim de Wit" <t.c...@gmail.com> wrote:
After updating to the development version, i get the following errors in my conquest logging:

openrem-rdsr: /var/lib/conquest-dicom-server/incoming/1.3.12.2.1107.5.1.4.75508.30000018010117412872200000200.dcm
Traceback (most recent call last):
  File "/usr/local/bin/openrem_rdsr.py", line 23, in <module>
    rdsr(filename)
TypeError: 'module' object is not callable
openrem-rdsr: /var/lib/conquest-dicom-server/incoming/1.3.12.2.1107.5.1.4.95841.30000017122609185966600007384.dcm
Traceback (most recent call last):
  File "/usr/local/bin/openrem_dx.py", line 23, in <module>
    dx(filename)
TypeError: 'module' object is not callable

I get this for all import scripts. Any ideas?

--
You received this message because you are subscribed to the Google Groups "OpenREM" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openrem+u...@googlegroups.com.

Ed McDonagh

unread,
Jan 11, 2018, 9:07:24 AM1/11/18
to Tim de Wit, OpenREM
Fix has now been committed to develop :-)

To unsubscribe from this group and stop receiving emails from it, send an email to openrem+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages