Ok, that sounds reasonable. Even better would be to ask the user for the basedir (one should check that this is a proper directory) and write a default config file containing
I'm not so sure that blocking waiting for input is a good idea. What about when the user starts it from a gui shortcut with IO thats been redirected somewhere. It would then appear to hang.
I just removed trailing whitespaces, I hope this didn't create too much problems for you.
Ah thats probally why I couldn't see anything. I'll try to clean future patches.
PS: We should really wait for the inclusion of the separate UI patch until the 2.3.0 version has been released. The following patch could go in though. I'll create a 2.3 branch when the 2.3.0 version has been released.
I expected that. I'm in no rush.
| If you want to pass a default user config file, why don't you | pass it together with the site-wide config file to | the setupconfigparser method.
My goal here was to change as little as possible of what you had yet allow for using a config file that is names differently. But I can re-factor a bit if you like. You are suggesting refactoring to remove the Global?
+def processconfig(defconfigfile = "/etc/pytonerc"):
| I would call this siteconfigfile
I was trying to keep it obvious that is was a default for the configfile option. But sure thats fine.