![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Is someone taking care about the fact that the pgdb.py shipped with 7.4.1 is the wrong version? |
#3
| |||
| |||
|
|
Gaetano Mendola <mendola (AT) bigfoot (DOT) 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? |
#4
| |||
| |||
|
|
On Monday 02 February 2004 10:54 pm, Tom Lane wrote: Gaetano Mendola <mendola (AT) bigfoot (DOT) 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. |
#5
| |||
| |||
|
|
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: |
![]() |
| Thread Tools | |
| Display Modes | |
| |