Startup - No handlers could be found for logger "dicompyler"

[GoogleCodeExporter]

What steps will reproduce the problem?
1.Starting Dicompyler 0.4.1

What is the expected output? What do you see instead?
Starting the program it exit with an error
According to the logfile
No handlers could be found for logger "dicompyler".

I tried to launch it from the source (main.py), resulting with the same error

What version of the product are you using? On what operating system?
Windows 7 (64 bit)
Python 2.7 (32 bit)
dicompyler 0.4.1 (binary) or running from source)

Please provide any additional information below.

Original issue reported on code.google.com by Akos.Gul...@gmail.com on 1 Jan 2012 at 3:35

[GoogleCodeExporter]

I had this same problem when trying to use the installed version of dicomplyer 
using easy_install on Ubuntu 10.04 which I believe installed as a local user. I 
then uninstalled and tried to run the source through python, but had to re 
install the dicompyler mod again using easy_install for this to work as a 
missing module error arose. It then worked fine with logging; running in python 
trough the terminal.

Also was there documentation added explaining the plugin folder support? I was 
confused when adding items to baseplugins failed to cache. 

Super excited about the new release!

Original comment by lstrd...@gmail.com on 1 Jan 2012 at 3:46

[GoogleCodeExporter]

Interesting. I installed the binary version using a brand new restricted user 
on Windows 7 64 and it worked without any issues.

Can you guys try using "dicompyler_app.py" in the source directory? This is now 
the preferred way to start dicompyler. Using "main.py" may not work anymore. If 
you installed using the Python package (i.e. easy_install or pip) you should 
have gained a command on your path called "dicompyler".

Regarding plugin folder support, the only thing that should have changed are 
any import statements that use modules from dicompyler should be rewritten:

i.e. import guiutil should now be from dicompyler import guiutil

Also, this release should allow you to move the user plugins folder. This means 
you can make a directory for the user plugins anywhere you like, and point 
dicompyler to that folder using the setting in preferences. You will need to 
point the location to one folder above your folder so it can pick it up. This 
is the preferred way to use 3rd-party plugins.

I have not tested any folder plugins in the baseplugins folder, but they should 
work fine with the above change.

Original comment by bastula on 1 Jan 2012 at 4:09

• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Hello,

I don't have dicompyler_app.py in my source directory, now I am trying to 
install easy_install, see If I have any missing part.

Original comment by Akos.Gul...@gmail.com on 1 Jan 2012 at 4:12

[GoogleCodeExporter]

Ok, found the problem. Apparently on a new system, the "~/.dicompyler" folder 
on linux and "C:\Users\yourusername\AppData\Local\dicompyler\" folder on 
Windows 7, et. al. does not get created before the logging system is 
instantiated.

I forgot to delete my existing "~/.dicompyler" folder before testing.

A quick fix is to create this folder on your system before running for the 
first time.

You can see the appropriate folder to be created for your specific system on 
this page:
http://code.google.com/p/dicompyler/wiki/PluginDevelopmentGuide#Plugin_File_Stru
cture

I will to update the source to fix this, test and re-release new binaries.

Thanks for catching this early guys.

Original comment by bastula on 1 Jan 2012 at 4:19

• Changed state: Accepted

[GoogleCodeExporter]

This issue was closed by revision db28e5def78e.

Original comment by bastula on 1 Jan 2012 at 4:29

• Changed state: Fixed