Hi Dag,
On 05.06.05, Dag Wieers wrote:
On Sun, 29 May 2005, Joerg Lehmann wrote:
On 29.05.05, Dag Wieers wrote:
On Sun, 29 May 2005, Dag Wieers wrote:
I put a new tarball with the plugins online under the path I've send before. Testing is appreciated.
When building I get this:
[root@emyn PyTone-2.2.3+]# ./setup.py build running build running build_py package init file 'src/plugins/termtitle/__init__.py' not found (or not a regular file) error: package directory 'src/plugins/audioscrobbler' does not exist
After removing both plugins from setup.py it is ok. I thought you mentioned that you added the new plugins ?
I still wait for permission to distribute the audioscrobbler plugin. The termtitle plugin is no longer a package, but I did not yet fix the setup.py file.
Then when running:
[dag@emyn ~]$ pytone Traceback (most recent call last): File "/usr/lib/python2.3/site-packages/pytone/pytone.py", line 57, in ? config.processconfig() File "/usr/lib/python2.3/site-packages/pytone/config.py", line 905, in processconfig processstandardconfig() File "/usr/lib/python2.3/site-packages/pytone/config.py", line 759, in processstandardconfig readconfigsection(section, eval(section)) File "/usr/lib/python2.3/site-packages/pytone/config.py", line 699, in readconfigsection raise ConfigError("Unkown configuration option '%s' in section '%s'" % config.ConfigError: Unkown configuration option 'server' in section 'network'
After removing the server option in the network section I got another backtrace which is related to the window size of the xterm. Apparently 80x25 is still not sufficient for pytone on startup ?
The server option has been renamed (probably that's not really critical since not many people are using it).
For me, a terminal size of 80x24 works perfectly.
Also could you create it as 2.2.3.1 or something similar, not the plus sign, otherwise I have difficulties to package it properly. I'd like to create test packages of those releases too.
These test release are really just meant as a snapshot. I'm not sure whether it's a good idea to package them. Normally, I use a pre notation, but since I don't know yet whether the next release will be PyTone 2.3.0 or 2.2.4, I used the +.
PS: The problem with the ~/.pytone/plugins directory is, that there has to be an __init__.py file present (just create an empty one).
If I do this, it works but it will only recognize the plugins in my user-directory (~/.pytone/plugins) not the ones I have in the global directory.
Hey, that's what I have been looking at for the last ten minutes ;-). I don't understand what's going on there...
Also in this case, pytone bails out if it cannot find a plugin. It would be nicer to eg. display a message (maybe with: press enter to proceed) or just log the failure and continue.
Of course, but there are so many things to do and currently my free time is very limited.
Jörg