Issue 37 in goobook: version mismatch

5 views
Skip to first unread message

goo...@googlecode.com

unread,
Nov 13, 2012, 5:43:45 PM11/13/12
to goobook...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 37 by frantise...@gmail.com: version mismatch
http://code.google.com/p/goobook/issues/detail?id=37

What steps will reproduce the problem?
1. calling goobook query
2.
3.

What is the expected output? What do you see instead?

> Traceback (most recent call last):
> File "/usr/local/bin/goobook", line 9, in <module>
> load_entry_point('goobook==1.4.dev', 'console_scripts', 'goobook')()
>
> File "/usr/local/lib/python2.6/dist-packages/goobook-1.4.dev-py2.6.egg/goobook/application.py",
> line 83, in main
> args.func(config, args)
>
> File "/usr/local/lib/python2.6/dist-packages/goobook-1.4.dev-py2.6.egg/goobook/application.py",
> line 112, in
do_query
> goobk.query(args.query)
>
> File "/usr/local/lib/python2.6/dist-packages/goobook-1.4.dev-py2.6.egg/goobook/goobook.py",
> line 81, in query
> print (u'\t'.join((emailaddr, title,
> extra_str))).encode(self.__config.encoding, errors='replace')
> TypeError: encode() takes no keyword arguments


What version of the product are you using? On what operating system?
Distributor ID: Debian
Description: Debian GNU/Linux 6.0.6 (squeeze)
Release: 6.0.6
Codename: squeeze


Please provide any additional information below.

from my admin:



There is a problem in calling of encode() method, although valid in newer
python version, in version 2.6.x the keyword 'errors' cannot be used. When
removed, goobook works ok in Debian Squeeze default python version, please
update code to retain 2.6 compatibility.



goo...@googlecode.com

unread,
Nov 16, 2012, 6:26:33 AM11/16/12
to goobook...@googlegroups.com
Updates:
Status: WontFix

Comment #1 on issue 37 by h...@furuvik.net: version mismatch
http://code.google.com/p/goobook/issues/detail?id=37

Sorry, will not retain 2.6 compatibility there is also a library that need
to
be 2.6 compatible and even if it the parts used works at the moment that
will most
likely not continue to be the case.

Should also note that it's quite likely that the next version, whenever
that happens,
will require Python 3.3.

Reply all
Reply to author
Forward
0 new messages