Is someone taking care about the fact that the pgdb.py shipped with
7.4.1 is the wrong version? What bail me out is the fact that the
version pgdb.py shipped with 7.4.1 is a version *pre 7.3*; we
add the same "bug" with the 7.3 and was not solved until the 7.3.2
distribution:

http://archives.postgresql.org/pgsql...2/msg00082.php


Regards
Gaetano Mendola

Gaetano Mendola <mendola@bigfoot.com> writes:[color=blue]
> Is someone taking care about the fact that the pgdb.py shipped with
> 7.4.1 is the wrong version?[/color]

There is no pgdb.py in the core PG 7.4.* releases. I suppose you
are talking about a packaging error in the RPM distribution. Lamar Owen
would be the man to talk to about that ... Lamar, any thoughts about
this?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

On Monday 02 February 2004 10:54 pm, Tom Lane wrote:[color=blue]
> Gaetano Mendola <mendola@bigfoot.com> writes:[color=green]
> > Is someone taking care about the fact that the pgdb.py shipped with
> > 7.4.1 is the wrong version?[/color][/color]
[color=blue]
> There is no pgdb.py in the core PG 7.4.* releases. I suppose you
> are talking about a packaging error in the RPM distribution. Lamar Owen
> would be the man to talk to about that ... Lamar, any thoughts about
> this?[/color]

Well, my first instinct is to throw out the python client RPM entirely. Then
package the python client in a separate RPM. My original plan was not to
ship a python subpackage at all, but then I had a spec file change
contributed that kept the python client in. So I went that direction;
principle of least surprise and all. But I am not at all attached to keeping
it; likewise, the JDBC stuff could easily be moved to a completely separate
RPM instead of a subpackage.
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC 28772
(828)862-5554
www.pari.edu


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lamar Owen wrote:

| On Monday 02 February 2004 10:54 pm, Tom Lane wrote:
|
|>Gaetano Mendola <mendola@bigfoot.com> writes:
|>
|>>Is someone taking care about the fact that the pgdb.py shipped with
|>>7.4.1 is the wrong version?
|
|
|>There is no pgdb.py in the core PG 7.4.* releases. I suppose you
|>are talking about a packaging error in the RPM distribution. Lamar Owen
|>would be the man to talk to about that ... Lamar, any thoughts about
|>this?
|
|
| Well, my first instinct is to throw out the python client RPM
entirely. Then
| package the python client in a separate RPM. My original plan was not to
| ship a python subpackage at all, but then I had a spec file change
| contributed that kept the python client in. So I went that direction;
| principle of least surprise and all. But I am not at all attached to
keeping
| it; likewise, the JDBC stuff could easily be moved to a completely
separate
| RPM instead of a subpackage.


Is it not too late drop the python client RPM for the version 7.4 ?
Anyway the version pgdb.py in rpm with the version 7.3.2 is the good
one, I don't know where you get the wrong pgdb.py pre 7.3.2, isn't this
file in any CVS ?





Regards
Gaetano Mendola




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAH/Rh7UpzwH2SGd4RAkD9AKCg8dwii1r0xKXZxa8H3UZ2oVPY/QCfThtO
yFyk9wzD3uVFzkRF7GJiDJU=
=HQnJ
-----END PGP SIGNATURE-----


---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)

On Monday 02 February 2004 07:31 pm, Gaetano Mendola wrote:[color=blue]
> Is someone taking care about the fact that the pgdb.py shipped with
> 7.4.1 is the wrong version? What bail me out is the fact that the
> version pgdb.py shipped with 7.4.1 is a version *pre 7.3*; we
> add the same "bug" with the 7.3 and was not solved until the 7.3.2
> distribution:[/color]

7.4.2 as a tarball does not have pgdb.py in it. The RPMs for 7.4 and 7.4.1
mistakenly added the python client from a separate tarball. I will not be
adding this separate tarball this time; a separate python client RPM will
have to be built. The RPM's shouldn't editorialize, Tom Lane once said, and
including clients in the upstream RPMs that I distribute which are not in the
main tarball is editorializing (not to mention the fact that the tarball thus
inserted was of the wrong version, for which I apologize). I accepted the
contribution of this subpackage from Kaj last time; it will be gone for
7.4.2. Ask the python client maintainers for RPMs of their work. It's a
separate project on gborg.postgresql.org now, so a separate RPM for
postgresql-python will need to be built by someone in the python client gborg
project, or the other python client projects. I know that makes
distributors' lives harder (sorry Tom), but it really is necessary.

Summary: clients that are removed from the main tarball (such as the Pg module
and the python client) will in the future be consistently removed from the
RPMs of the main tarball. I once again apologize for not doing that for 7.4
and 7.4.1. For 7.5 this will be JDBC, right? (The JDBC RPM is pretty broken
anyway, and downloading the proper jar from jdbc.postgresql.org and making a
separate postgresql-jdbc RPM that is not a subpackage won't be hard).
--
Lamar Owen
Director of Information Technology
Pisgah Astronomical Research Institute
1 PARI Drive
Rosman, NC 28772
(828)862-5554
www.pari.edu

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster