Roundup Tracker - Issues

Issue 1779584

classification
alternative postgres port fails due to TypeError
Type: Severity: normal
Components: Database Versions:
process
Status: closed wont fix
:
: jpend : jpend
Priority: normal :

Created on 2007-08-22 17:25 by anonymous, last changed 2007-08-29 16:45 by jpend.

Files
File name Uploaded Description Edit Remove
back_postgresql.py.patch anonymous, 2007-08-22 17:25 workaround for int port number requirement
Messages
msg2469 Author: [hidden] (anonymous) Date: 2007-08-22 17:25
Setting the port of the postgres DB causes roundup to fail with a TypeError.  Specifically caught while running roundup-admin.  I have a simple (ugly) hack to back_postgresql.py that seems to work around this.


Traceback:

Traceback (most recent call last):
  File "/usr/local/bin/roundup-admin", line 3, in ?
    run()
  File "/usr/lib/python2.4/site-packages/roundup/scripts/roundup_admin.py", line 38, in run
    sys.exit(tool.main())
  File "/usr/lib/python2.4/site-packages/roundup/admin.py", line 1488, in main
    ret = self.run_command(args)
  File "/usr/lib/python2.4/site-packages/roundup/admin.py", line 1387, in run_command
    self.db = tracker.open('admin')
  File "/usr/lib/python2.4/site-packages/roundup/instance.py", line 90, in open
    vars = {
  File "/usr/lib/python2.4/site-packages/roundup/backends/rdbms_common.py", line 129, in __init__
    self.open_connection()
  File "/usr/lib/python2.4/site-packages/roundup/backends/back_postgresql.py", line 129, in open_connection
    db_create(self.config)
  File "/usr/lib/python2.4/site-packages/roundup/backends/back_postgresql.py", line 39, in db_create
    db_command(config, command)
  File "/usr/lib/python2.4/site-packages/roundup/backends/back_postgresql.py", line 58, in db_command
    conn = psycopg.connect(**template1)
  File "/usr/lib/python2.4/site-packages/psycopg2/psycopg1.py", line 34, in connect
    conn = _2psycopg.connect(*args, **kwargs)
TypeError: an integer is required
--

msg2470 Author: [hidden] (jpend) Date: 2007-08-28 03:29
This is fixed in psycopg2 2.0.5 (released 2006/09/04)

Bug: http://www.initd.org/tracker/psycopg/ticket/120
Checked in: http://www.initd.org/tracker/psycopg/changeset/807

I've verified that this works with postgres-8.2 and psycopg 2.0.5.1 (i.e. what I currently have installed on my ubuntu desktop)
msg2471 Author: [hidden] (jpend) Date: 2007-08-29 16:45
Closing since a released version of psycopg fixes this.
History
Date User Action Args
2007-08-22 17:25:08anonymouscreate