python-sybase-misc

Re: [Python-sybase-misc] How to set Sybase sets/tuples from Python?

[Deron M. <der...@gm...>]

On Tue, Aug 18, 2009 at 10:21 AM, <sk...@po...> wrote:
> Suppose I have this query:
>
>    select foo from bar where baz in ("A", "B", "C")
>
> and want to parameterize the where clause.  I've tried this:
>
>    query = 'select foo from bar where baz in "@type"'
>    args = {
>        "@type": ("A", "B", "C"),
>    }
>
> but I get a TypeError (unsupported parameter type) when I try to execute the
> query.

It's just a little more manual work on constructing your SQL.  You
have to make each item in the set a separate substitution, rather
than trying to use just one substitution with a tuple.

Say you have a list or set of items you want to match.  Then
try something like:

    items = ["A", "B", "C"]
    qitems = ", ".join( [ "@item%d" % n for n in range(len(items)) ] )
    query = "select foo from bar where baz in (" + qitems + ")
    args = dict( [ ("@item%d" % n, v) for n, v in enumerate(items) ] )

-- 
Deron Meranda

[Python-sybase-misc] How to set Sybase sets/tuples from Python?

[<sk...@po...>]

Suppose I have this query:

    select foo from bar where baz in ("A", "B", "C")

and want to parameterize the where clause.  I've tried this:

    query = 'select foo from bar where baz in "@type"'
    args = {
        "@type": ("A", "B", "C"),
    }

but I get a TypeError (unsupported parameter type) when I try to execute the
query.

I manually tried creating DataBuf objects from various container types but
they all failed:

     >>> sybase.DataBuf(1)
    <DataBufType object at 0x8366728>
    >>> sybase.DataBuf(())
    Traceback (most recent call last):
      File "<stdin>", line 1, in ?
    TypeError: unsupported parameter type
    >>> sybase.DataBuf([])
    Traceback (most recent call last):
      File "<stdin>", line 1, in ?
    TypeError: unsupported parameter type
    >>> sybase.DataBuf(set())
    Traceback (most recent call last):
      File "<stdin>", line 1, in ?
    TypeError: unsupported parameter type

We are using an old version of the Sybase module (0.36) so this might have
been something previously unsupported but which is supported in a later
version, however I thought I would ask what the proper syntax for this is.

Thx,

-- 
Skip Montanaro - sk...@po... - http://www.smontanaro.net/
    Getting old sucks, but it beats dying young

Re: [Python-sybase-misc] Using new sybase features from python-sybase

[Sébastien S. <sa...@us...>]

Hi Zsolt,

a similar problem has recently been reported by someone else in the bug 
tracker at the following url:
http://sourceforge.net/tracker/?func=detail&aid=2809032&group_id=184050&atid=907701

I will modify python-sybase in a coming version so that it supports all 
the functionalities of the Sybase version it is compiled with, by 
passing the maximum CS_VERSION_* value supported.

You can track this evolution in the bug tracker at the provided url.

regards

--
Sébastien Sablé

Cserna, Zsolt a écrit :
> Hi all,
> 
> We build python-sybase from source and would like to use the new features of sybase including kerberos authentication and large data fields (char, varchar sized over than 255 chars). As far as I know these features have been added to sybase openclient 12.5 and above, but not working for us with the original python-sybase source code.
> 
> Is it working for you with the original source? I mean the kerberos authentication and the large data fields.
> 
> It seemed to me that the extension contains some wired-in values, especially for ct_init and ct_alloc - both receive the version to be "emulated" as the first argument. Specifying the contstant CS_VERSION_100 (which I think means 10.0) to them as python-sybase does  limits the package's functionality to 10.0 - disabling the new features coming with 12.5 or 15.0.
> 
> I've modified these values to the values I needed and it's working for me, but these are still wired-in values, and I'm not entirely sure that that's the official solution for that.
> 
> Are there any plans in the future to auto-detect the version of the openclient library and specify the highest version possible to ct_alloc and ct_init in python-sybase?
> 
> Thanks,
> Zsolt
> 
> --------------------------------------------------------------------------
> NOTICE: If received in error, please destroy, and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. We may monitor and store emails to the extent permitted by applicable law.
> 
> ------------------------------------------------------------------------------
> Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
> trial. Simplify your report design, integration and deployment - and focus on 
> what you do best, core application coding. Discover what's new with 
> Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

[Python-sybase-misc] Unknown data format when selecting len(convert(varbinary(MAX)...))

[Deron M. <der...@gm...>]

I have pysybase 0.38 connecting to a SQL Server database.

There is a table with a blob/image column, say:

  table A
     a_id   int(10)  not null primary key;
     a_blob   image(2147483647)  null;

Trying to get the length of the image, I found this works:

   select datalength(a_blob) from A where a_id = 12345;

but the following supposedly equivalent SQL will raise a TypeError

   select len(convert(varbinary(MAX), a_blob)) from A where a_id = 12345;


The above SQL though works at a SQL prompt...using freetds,
but not with the python-sybase interface.


Digging down in Sybase.py the error is coming from the
_extract_row() function, where it is trying to reference "buf[n]"

In this case:
   n = 0
   buf = <DataBufType object at 0xb7acd980>
   buf.datatype = 30
   buf.format = 0
   buf[n] = ..... TypeError: unknown data format

Any ideas?
-- 
Deron Meranda

[Python-sybase-misc] Using new sybase features from python-sybase

[Cserna, Z. <Zso...@Mo...>]

Hi all,

We build python-sybase from source and would like to use the new features of sybase including kerberos authentication and large data fields (char, varchar sized over than 255 chars). As far as I know these features have been added to sybase openclient 12.5 and above, but not working for us with the original python-sybase source code.

Is it working for you with the original source? I mean the kerberos authentication and the large data fields.

It seemed to me that the extension contains some wired-in values, especially for ct_init and ct_alloc - both receive the version to be "emulated" as the first argument. Specifying the contstant CS_VERSION_100 (which I think means 10.0) to them as python-sybase does  limits the package's functionality to 10.0 - disabling the new features coming with 12.5 or 15.0.

I've modified these values to the values I needed and it's working for me, but these are still wired-in values, and I'm not entirely sure that that's the official solution for that.

Are there any plans in the future to auto-detect the version of the openclient library and specify the highest version possible to ct_alloc and ct_init in python-sybase?

Thanks,
Zsolt

--------------------------------------------------------------------------
NOTICE: If received in error, please destroy, and notify sender. Sender does not intend to waive confidentiality or privilege. Use of this email is prohibited when received in error. We may monitor and store emails to the extent permitted by applicable law.

[Python-sybase-misc] Getting error sp_cursoropen: The value of the parameter 'scrollopt' is invalid.

[Deron M. <der...@gm...>]

I'm running
* Linux 2.4
* Python 2.3
* freetds 0.82
* python sybase 0.39

When I try to execute any query, I get the following error:

>>> import Sybase
>>> d = Sybase.connect( dsn='XXX', user='XXX', passwd='XXX', database='XXX', auto_commit=0 )
>>> c = d.cursor()
>>> c.execute("select count(*) from INFORMATION_SCHEMA.TABLES")
Traceback (most recent call last):
  File "<stdin>", line 1, in ?
  File "build/bdist.linux-i686/egg/Sybase.py", line 546, in execute
  File "build/bdist.linux-i686/egg/Sybase.py", line 695, in _start
  File "build/bdist.linux-i686/egg/Sybase.py", line 709, in _mainloop
  File "build/bdist.linux-i686/egg/Sybase.py", line 753, in _raise_error
Sybase.DatabaseError: Msg 16902, Level 16, State 24, Line 1
sp_cursoropen: The value of the parameter 'scrollopt' is invalid.

This worked with previous versions (freetds 0.63 and python sybase 0.38).

Also, I think freetds is itself working because I also have sqsh
compiled against it, and sqsh can do queries without error.


Does anybody have any ideas what this is, or how I could fix it?
-- 
Deron

Re: [Python-sybase-misc] Getting error sp_cursoropen: The value of the parameter 'scrollopt' is invalid.

[Deron M. <der...@gm...>]

On Wed, Jul 29, 2009 at 3:00 PM, Deron Meranda<der...@gm...> wrote:
> Sybase.DatabaseError: Msg 16902, Level 16, State 24, Line 1
> sp_cursoropen: The value of the parameter 'scrollopt' is invalid.


I just tried python-sybase 0.38, and it works (with the same
freetds 0.82).

So this error is cropping up between 0.38 and 0.39.

Deron

[Python-sybase-misc] Building 0.39 on Mac OS X 10.5.7?

[Edward J. S. <ejs...@ma...>]

I'm trying to run the 0.39 installer on Mac OS X 10.5.7 (Intel x86_64)  
using Python 2.6 with Sybase ASE 12.5, however it fails during the  
build_ext portion.

My pertinent env variables:

SYBASE=/Applications/Sybase
SYBASE_OCS=/Applications/Sybase/System/OCS-12_5

The install output and errors:

$ python setup.py install
running install
running bdist_egg
running egg_infowriting python_sybase.egg-info/PKG-INFO
writing top-level names to python_sybase.egg-info/top_level.txt
writing dependency_links to python_sybase.egg-info/dependency_links.txt
reading manifest file 'python_sybase.egg-info/SOURCES.txt'
writing manifest file 'python_sybase.egg-info/SOURCES.txt'
installing library code to build/bdist.macosx-10.3-fat/egg
running install_lib
running build_py
running build_ext
building 'sybasect' extension
gcc -arch ppc -arch i386 -isysroot /Developer/SDKs/MacOSX10.4u.sdk - 
fno-strict-aliasing -fno-common -dynamic -DNDEBUG -g -O3 - 
DWANT_BULKCOPY -DHAVE_DATETIME -DHAVE_DECIMAL -DHAVE_BLK_ALLOC - 
DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP -DHAVE_BLK_ROWXFER_MULT - 
DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR -DHAVE_CT_DATA_INFO - 
DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA -DHAVE_CT_SETPARAM -DHAVE_CS_CALC  
-DHAVE_CS_CMP -I/Applications/Sybase/System/OCS-12_5/include -I/ 
Library/Frameworks/Python.framework/Versions/2.6/include/python2.6 -c  
sybasect.c -o build/temp.macosx-10.3-fat-2.6/sybasect.o
sybasect.c: In function ‘initsybasect’:sybasect.c: In function  
‘initsybasect’:
sybasect.c:1610: error: ‘PyDateTime_IMPORT’ undeclared (first use in  
this function)
sybasect.c:1610: error: (Each undeclared identifier is reported only  
once
sybasect.c:1610: error: for each function it appears in.)
sybasect.c:1610: error: ‘PyDateTime_IMPORT’ undeclared (first use in  
this function)
sybasect.c:1610: error: (Each undeclared identifier is reported only  
once
sybasect.c:1610: error: for each function it appears in.)
lipo: can't figure out the architecture type of: /var/folders/6Z/ 
6ZK5YgTNHCe20-NdXh20gE+++TI/-Tmp-//cc9VPG2i.out
error: command 'gcc' failed with exit status 1

Anyone have any ideas?

Re: [Python-sybase-misc] How to obtain the return status of a stored procedure?

[Sébastien S. <sa...@us...>]

Hi Jeffrey,

you obtain the return status of a stored procedure this way:

status = cursor.callproc(procname,args)

regards

--
Sébastien Sablé

Jeffrey Zelt a écrit :
> I have a simple question:
> 
>  
> 
> How do I obtain the return status of a Sybase stored procedure?
> 
>  
> 
> By return status, I mean the integer value that is returned by the 
> “return” statement of a Sybase stored procedure.
> 
>  
> 
> Let us say I execute a stored procedure using:
> 
>  
> 
>    cursor.callproc(‘storedprocname’, ...)
> 
>  
> 
> Is there any way to obtain the return status of this call?
> 
>  
> 
> I have searched and searched and searched, but I have not found the 
> answer.  It seems to be a simple question.  Is the answer complex?
> 
>  
> 
> Very perplexed,
> 
> Jeffrey
> 
> 
> ------------------------------------------------------------------------
> 
> ------------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

[Python-sybase-misc] How to obtain the return status of a stored procedure?

[Jeffrey Z. <Jef...@q-...>]

I have a simple question:

 

How do I obtain the return status of a Sybase stored procedure?

 

By return status, I mean the integer value that is returned by the
"return" statement of a Sybase stored procedure.

 

Let us say I execute a stored procedure using:

 

   cursor.callproc('storedprocname', ...)

 

Is there any way to obtain the return status of this call?

 

I have searched and searched and searched, but I have not found the
answer.  It seems to be a simple question.  Is the answer complex?

 

Very perplexed,

Jeffrey 

Re: [Python-sybase-misc] Installing python-sybase on Linux - SUCCESS!

[Jeffrey Z. <Jef...@q-...>]

Bingo!  That was the tip I needed.  I have now successfully connected to
one of our Sybase servers with python-sybase.  

 

By the way, it was only necessary for me to place the line:

 

    /opt/sybase/OCS-15_0/lib/

 

in a file that ldconfig could process.  It was _not_ necessary to
include the second line:

 

    /opt/sybase/OCS-15_0/devlib/

 

Thank you for your help, as well as to others who also tried to assist
me!

 

Regards,

Jeffrey Zelt

Q-Free ASA

 

 

The install seemed to go OK, but when I try to import the Sybase module
in a Python interpreter, I see the following exception:
  

<snip>



As you can see, it is complaining that it cannot find the shared library
"libsybtcl.so".  I have looked on my machine and there is a copy of
libsybtcl.so in both of these directories:
 
    /opt/sybase/OCS-15_0/lib/   
    /opt/sybase/OCS-15_0/devlib/
  

I'd guess, off hand, that neither of those directories is in the dynamic
library path unless you're logged in as sybase (and have ensured that
your .bashrc [or appropriate file] includes a call to source
/opt/sybase/SYBASE.sh [or the equivalent if you use the Korn shell]).

Now, you might also simply add those directories to the system dynamic
library path:
(I think this is pretty universal across different Linux versions, but
you can check via man ldconfig.) Create a file called (for instance)
/etc/ld.so.conf.d/sybase.conf with these two lines:



/opt/sybase/OCS-15_0/lib/
/opt/sybase/OCS-15_0/devlib/
 

Then run ldconfig. You should be in business. 

[Python-sybase-misc] Sybase hang with cursors

[Abel Q. <bel...@ho...>]

Hello,

I am experiencing what appears to be a Sybase ASE hang when executing a 
particular query. When executing that query from another db client (Aqua 
Data Studio), the query takes about 3-4 seconds to complete, but from Python 
it simply never completes. The Sybase host is in Linux. Below I show some 
details of the call as well as the output of a stored proc that shows 
information about sybase processes.

I also bring to your attention that the same query to Sybase on a Solaris 
machine works fine. It does not hang.

What could I do to get rid of this problem?

I contacted the dba's in our organization. Their response was that they do 
not support CURSORS in SYBASE because they are difficult to debug and 
analize, and that was the end of it.

-----------------------------------
the Python sequence:
db = Sybase.connect('NYFICCTP02', 'quiroa', 'AbelQuiros')
c = db.cursor()
c.execute("select CustomerId from BeneficialOwner where 
BeneficialOwner='640935301'")

-----------------------------------
the output of stored proc that shows process info:
spid     loginame  db.table                                       locktype 
page            status       hostprocess   program    cmd
------- --------- -----------------------------        -----------  --------- 
      ---------  ------------  ----------   ------------
2374   quiroa      ConfTrack.CommDirectory         Sh_intent    0 
running    :4928                                FETCH CURSOR
2374   quiroa      ConfTrack.CommDirectory         Sh_page     134095302 
running    :4928                                FETCH CURSOR
2374   quiroa      ConfTrack.PmtCustomer             Sh_intent    0 
running    :4928                                FETCH CURSOR
2374   quiroa      ConfTrack.PmtCustomer             Sh_page     16434233 
running    :4928                                FETCH CURSOR
2374   quiroa      amhub.ACCOUNT                     Sh_intent    0 
running    :4928                                FETCH CURSOR
2374   quiroa      amhub.ACCOUNT                     Sh_page     2684147 
running    :4928                                FETCH CURSOR
2374   quiroa      entity_master.AltIdCombined       Sh_intent    0 
running    :4928                                FETCH CURSOR
2374   quiroa      entity_master.AltIdCombined       Sh_page     377944 
running    :4928                                FETCH CURSOR
2374   quiroa      entity_master.AltIdCombined       Sh_page     377946 
running    :4928                                FETCH CURSOR
2374   quiroa      entity_master.EAR_AccountRole Sh_intent     0 
running    :4928                                FETCH CURSOR
2374   quiroa      entity_master.EAR_AccountRole Sh_page      235696 
running    :4928                                FETCH CURSOR
2374   quiroa      entity_master.EAR_PickList        Sh_intent      0 
running    :4928                                FETCH CURSOR
2374   quiroa      entity_master.EAR_PickList        Sh_page       332666 
running    :4928                                FETCH CURSOR 

Re: [Python-sybase-misc] Installing python-sybase on Windows XP

[Abel Q. <bel...@ho...>]

>I have also tried using the latest version of Python 2.6.x, but the
>installation fails with
>
>running build_ext
>building 'sybasect' extension
>error: None

To install it on Python 2.6, you need to get the VC++ 2008 Express Edition. 
After you install it, run the python sybase install script from within the 
Visual Studio 2008 Command Prompt shell. A shortcut to it is supposed to be 
available inside the VC++2008 folder under Start > Programs

If this does not work as expected (which happened to me on one workstation), 
I manually ran the target of the Visual Studio 2008 Command Prompt shortcut 
on a command prompt and then ran the python sybase install script.

Please, let me know how it goes. 

Re: [Python-sybase-misc] Change in query behaviour?

[Bond, G. <Gre...@it...>]

It's a regression from the refactoring that happened in 0.39.  See

https://sourceforge.net/tracker/?func=detail&aid=2165436&group_id=184050&atd
=907701

https://sourceforge.net/mailarchive/forum.php?thread_name=C52210F9.5BA04%25G
regory.Bond%40itg.com&forum_name=python-sybase-misc


On 26/03/09 8:31 AM, "Glen Jackson" <gl...@be...> wrote:

> After upgrading to ASE 15 and reinstalling python-sybase, my existing
> scripts stopped working. The problem seems to be that the
> "connection.query( sql )" method always returns None.  A few key strokes
> to change that to a cursor query and everything works fine - so the
> connection is good, the query string is valid and there is no problem
> with permissions.  (The only real problem is that I have a strong
> aversion to using cursors for simple queries that just return a single
> simple value.)
> 
> Has this behavior, or the syntax, changed in python-sybase 0.39?
> 
> Glen Jackson
> =========
> IST-Data Services
> UC, Berkeley
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

-- 
Gregory Bond
Vice President
Product Manager, Middle & Back Office Systems
ITG Australia Limited
Investment Technology Group, Inc.
--------------------------
Level 3, Rialto North Tower
525 Collins Street
Melbourne VIC 3000
AUSTRALIA

Ph. +61 3 9211 2518
Fax: +61 3 9211 2599

www.itg.com

[Python-sybase-misc] Change in query behaviour?

[Glen J. <gl...@be...>]

After upgrading to ASE 15 and reinstalling python-sybase, my existing
scripts stopped working. The problem seems to be that the
"connection.query( sql )" method always returns None.  A few key strokes
to change that to a cursor query and everything works fine - so the
connection is good, the query string is valid and there is no problem
with permissions.  (The only real problem is that I have a strong
aversion to using cursors for simple queries that just return a single
simple value.)

Has this behavior, or the syntax, changed in python-sybase 0.39? 

Glen Jackson
=========
IST-Data Services
UC, Berkeley

Re: [Python-sybase-misc] Installing python-sybase on Linux - *almost* successful

[Lloyd K. <py...@ve...>]

On Wed, 2009-03-25 at 14:09 +0100, Jeffrey Zelt wrote:
> Having failed at installing python-sybase on Windows, I decided to
> give it a go on Linux (Ubuntu 8.10).
> 
Just use the package manager!
>From the Menus:
        System/Administration/Synaptic
If you put sybase in the search box, you'll quickly find python-pymssql.

Make sure that Synaptic is searching the community supported
repositories:
        Settings/Repositories/[Ubuntu Software TAB]/Community...checkbox

Linux system administration is dead simple if you just use the package
management tools.

<True Confessions>I'm actually running python-sybase on an older server
where I did have to compile it myself.</True>

-- 
Lloyd Kvam
Venix Corp
DLSLUG/GNHLUG library
http://dlslug.org/library.html
http://www.librarything.com/catalog/dlslug
http://www.librarything.com/rsshtml/recent/dlslug
http://www.librarything.com/rss/recent/dlslug

Re: [Python-sybase-misc] Installing python-sybase on Linux - *almost* successful

[John M. C. <jm...@xm...>]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000099">
<br>
<br>
Jeffrey Zelt wrote:<br>
&lt;snip&gt;<br>
<blockquote
 cite="mid:F8E...@MX..."
 type="cite">
  <pre wrap="">
The install seemed to go OK, but when I try to import the Sybase module
in a Python interpreter, I see the following exception:
  </pre>
</blockquote>
&lt;snip&gt;<br>
<blockquote
 cite="mid:F8E...@MX..."
 type="cite">
  <pre wrap="">As you can see, it is complaining that it cannot find the shared library
"libsybtcl.so".  I have looked on my machine and there is a copy of
libsybtcl.so in both of these directories:

    /opt/sybase/OCS-15_0/lib/   
    /opt/sybase/OCS-15_0/devlib/
  </pre>
</blockquote>
I'd guess, off hand, that neither of those directories is in the
dynamic library path unless you're logged in as sybase (and have
ensured that your .bashrc [or appropriate file] includes a call to
source /opt/sybase/SYBASE.sh [or the equivalent if you use the Korn
shell]).<br>
<br>
Now, you might also simply add those directories to the system dynamic
library path:<br>
(I think this is pretty universal across different Linux versions, but
you can check via man ldconfig.) Create a file called (for instance)
/etc/ld.so.conf.d/sybase.conf with these two lines:<br>
<pre wrap="">/opt/sybase/OCS-15_0/lib/
/opt/sybase/OCS-15_0/devlib/

</pre>
Then run ldconfig. You should be in business. <br>
<br>
Alternatively, you could add soft links to libsybtcl.so in the lib
directories used by Python (or just in /usr/lib ).<br>
<br>
HTH!<br>
<br>
JMC<br>
</body>
</html>

Re: [Python-sybase-misc] Installing python-sybase on Linux - *almost* successful

[<sk...@po...>]

    Jeffrey> What I have done is:

    Jeffrey>   1. Installed Sybase ASE 15.02 Express Edition
    Jeffrey>      (ase1502_xe_linux.tgz)

    Jeffrey>   2. Installed the header files for Python 2.5

    Jeffrey>   3. Installed python-sybase (with "python setup.py install" as
    Jeffrey>      root)

Replace #3 with

    python setup.py build_ext -R /opt/sybase/OCS-15_0 -L /opt/sybase/OCS-15_0
    python setup.py install

or run the interpreter with /opt/sybase/OCS-15_0 in LD_LIBRARY_PATH.

-- 
Skip Montanaro - sk...@po... - http://www.smontanaro.net/

[Python-sybase-misc] Installing python-sybase on Linux - *almost* successful

[Jeffrey Z. <Jef...@q-...>]

Having failed at installing python-sybase on Windows, I decided to give
it a go on Linux (Ubuntu 8.10).

I think I have *almost* succeeded, but it does not "quite" work.  I hope
someone can give me a pointer to get me going.

What I have done is:

  1. Installed Sybase ASE 15.02 Express Edition (ase1502_xe_linux.tgz)

  2. Installed the header files for Python 2.5

  3. Installed python-sybase (with "python setup.py install" as root)


The install seemed to go OK, but when I try to import the Sybase module
in a Python interpreter, I see the following exception:

    jeffreyz@jeffreyz-Ubuntu-8:~$ python
    Python 2.5.2 (r252:60911, Oct  5 2008, 19:24:49) 
     [GCC 4.3.2] on linux2
    Type "help", "copyright", "credits" or "license" for more
information.
    >>> import Sybase
    Traceback (most recent call last):
      File "<stdin>", line 1, in <module>
      File "build/bdist.linux-i686/egg/Sybase.py", line 11, in <module>
      File "build/bdist.linux-i686/egg/sybasect.py", line 7, in <module>
      File "build/bdist.linux-i686/egg/sybasect.py", line 6, in
__bootstrap__
    ImportError: libsybtcl.so: cannot open shared object file: No such
file or directory
    >>>


As you can see, it is complaining that it cannot find the shared library
"libsybtcl.so".  I have looked on my machine and there is a copy of
libsybtcl.so in both of these directories:

    /opt/sybase/OCS-15_0/lib/   
    /opt/sybase/OCS-15_0/devlib/

I do not understand what is wrong. 
 

  1. Was there, in fact, a problem with the build of python-sybase?
     If so, please indicate how I can fix this problem.

  2. Was the build OK, but I need to configure something else after the
build
     (so that it finds libsybtcl.so)? If so, please indicate what I can
do.  


Many thanks in advance.  I think I am getting close, but I will be stuck
without a little help.

Jeffrey Zelt
QFree ASA

Re: [Python-sybase-misc] Installing python-sybase on Windows XP

[<sk...@po...>]

    Jeffrey> First of all, the installation documents states that the
    Jeffrey> "Micorsoft Visual C++ 2005 Express Edition compiler can be
    Jeffrey> freely downloaded and used".  I have done that and when I try
    Jeffrey> to install python-sybase on Windows (with Python 2.5.4), I get
    Jeffrey> the following error:

    Jeffrey>     error: Python was built with Visual Studio 2003;
    Jeffrey>     extensions must be built with a compiler than can generate
    Jeffrey> compatible binaries.
    Jeffrey>     Visual Studio 2003 was not found on this system. If you have Cygwin
    Jeffrey> installed
    Jeffrey>     you can try compiling with MingW32, by passing "-c mingw32" to
    Jeffrey> setup.py.

    Jeffrey> I do not have access to Visual Studio 2003.

How about building Python with the Visual C++ 2005 Express Edition or
building Python and the Sybase extension with Cygwin?

(Like Sébastien, I don't use Windows, so I can only offer suggestions, not
give you a concrete set of instructions.)

-- 
Skip Montanaro - sk...@po... - http://www.smontanaro.net/

Re: [Python-sybase-misc] Installing python-sybase on Windows XP

[Sébastien S. <sa...@us...>]

Hi Jeffrey,

I do not use windows myself, but as far as I know you should use the 
same compiler to compile python-sybase than the one that was used to 
compile Python.

python-sybase uses distutils for compilation in a standard way so you 
will probably experience the same problem with any python package which 
contains a C extension and you can follow any existing tutorial on 
compiling a C extension for Python in windows to compile python-sybase.

Here is a good start:
http://docs.python.org/extending/windows.html
http://boodebr.org/main/python/build-windows-extensions

regards

--
Sébastien Sablé

Jeffrey Zelt a écrit :
> Is it possible to install the python-sybase module on Windows XP?
> 
> I have tried on and off for 2 years and I have never been successful,
> even though I have followed the instructions at:  
> 
>     http://python-sybase.sourceforge.net/install.html
> 
> This information is clearly wrong and I would appreciated it *very much*
> if a single reader of this list would help me.
> 
> First of all, the installation documents states that the "Micorsoft
> Visual C++ 2005 Express Edition compiler can be freely downloaded and
> used".  I have done that and when I try to install python-sybase on
> Windows (with Python 2.5.4), I get the following error:
> 
>     error: Python was built with Visual Studio 2003;
>     extensions must be built with a compiler than can generate
> compatible binaries.
>     Visual Studio 2003 was not found on this system. If you have Cygwin
> installed
>     you can try compiling with MingW32, by passing "-c mingw32" to
> setup.py.
> 
> I do not have access to Visual Studio 2003.
> 
> I have also tried using the latest version of Python 2.6.x, but the
> installation fails with
> 
>     running build_ext
>     building 'sybasect' extension
>     error: None
> 
> This is extremely frustrating.  Is there *any* way I can install
> python-sybase on Windows?
> 
> Our company uses Sybase for large projects and I would like to use
> Python for development purposes.
> 
> I hope there is at least one person out there who has managed to
> successfully install python-sybase with Python 2.5.x on Windows.  If so,
> I would very much like to know what I am doing wrong.
> 
> Many, many thanks in advance.
> 
> Jeffrey Zelt
> QFree ASA 
> 
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc

[Python-sybase-misc] Installing python-sybase on Windows XP

[Jeffrey Z. <Jef...@q-...>]

Is it possible to install the python-sybase module on Windows XP?

I have tried on and off for 2 years and I have never been successful,
even though I have followed the instructions at:  

    http://python-sybase.sourceforge.net/install.html

This information is clearly wrong and I would appreciated it *very much*
if a single reader of this list would help me.

First of all, the installation documents states that the "Micorsoft
Visual C++ 2005 Express Edition compiler can be freely downloaded and
used".  I have done that and when I try to install python-sybase on
Windows (with Python 2.5.4), I get the following error:

    error: Python was built with Visual Studio 2003;
    extensions must be built with a compiler than can generate
compatible binaries.
    Visual Studio 2003 was not found on this system. If you have Cygwin
installed
    you can try compiling with MingW32, by passing "-c mingw32" to
setup.py.

I do not have access to Visual Studio 2003.

I have also tried using the latest version of Python 2.6.x, but the
installation fails with

    running build_ext
    building 'sybasect' extension
    error: None

This is extremely frustrating.  Is there *any* way I can install
python-sybase on Windows?

Our company uses Sybase for large projects and I would like to use
Python for development purposes.

I hope there is at least one person out there who has managed to
successfully install python-sybase with Python 2.5.x on Windows.  If so,
I would very much like to know what I am doing wrong.

Many, many thanks in advance.

Jeffrey Zelt
QFree ASA 

Re: [Python-sybase-misc] "ImportError: .../sybasect.so: undefined symbol: cs_config"

[Sébastien S. <sa...@us...>]

Hi Terry,

thanks for the feedback.

There are different naming conventions for sybase libraries depending on 
the version of sybase, the platform, 32 or 64 bits and if you are using 
the original sybase libraries or freetds...

I have commited a correction in trunk which hopefully should work in 
most cases:


$ svn diff
Index: setup.py
===================================================================
--- setup.py	(révision 443)
+++ setup.py	(copie de travail)
@@ -90,7 +90,7 @@
      for name in lib_names:
          extensions = [('', 'a'), ('', 'so'), ('_r', 'a'), ('_r', 'so')]
          if have64bit and sys.platform not in ['osf1V5']:
-            extensions = [('_r64', 'a'), ('_r64', 'so')]
+            extensions = [('_r64', 'a'), ('_r64', 'so')] + extensions
          for (ext1, ext2) in extensions:
              lib_name = "%s%s" % (name, ext1)
              lib_path = os.path.join(sybase, 'lib', 'lib%s.%s' % 
(lib_name, ext2))
Index: ChangeLog
===================================================================
--- ChangeLog	(révision 443)
+++ ChangeLog	(copie de travail)
@@ -1,3 +1,7 @@
+2009-03-06  Sébastien Sablé  <sa...@us...>
+
+	* setup.py: Improved libraries detection for 64bits platforms
+
  2008-10-15  Sébastien Sablé  <sa...@us...>

  	* Sybase.py: Start using logging module



$ svn commit -m "Improved libraries detection for 64bits platforms"
Envoi          ChangeLog
Envoi          setup.py
Transmission des données ..
Révision 444 propagée.


regards

--
Sébastien Sablé

Terry Burton a écrit :
> On Fri, Mar 6, 2009 at 1:25 PM, Sébastien Sablé
> <sa...@us...> wrote:
>> the sybase module is not linked to the freetds libraries, that is why there
>> are some undefined symbols.
>>
>> This is probably because the setup.py script is not looking with the correct
>> name for those libraries.
> 
> Hi Sébastien,
> 
> Absolutely correct, thanks.
> 
> Commenting out the lines that append _r64 to the lib path for 64-bit
> arch fixes the problem:
> 
> if os.name == 'posix':                  # unix
>     # Most people will define the location of their Sybase
>     # installation in their environment.
> ...
>     lib_names += ['sybblk', 'sybct', 'sybcs', 'sybtcl', 'sybinsck',
> 'sybcomn', 'sybintl', 'sybunic']
>     for name in lib_names:
>         extensions = [('', 'a'), ('', 'so'), ('_r', 'a'), ('_r', 'so')]
> #        if have64bit and sys.platform not in ['osf1V5']:
> #            extensions = [('_r64', 'a'), ('_r64', 'so')]
>         for (ext1, ext2) in extensions:
>             lib_name = "%s%s" % (name, ext1)
>             lib_path = os.path.join(sybase, 'lib', 'lib%s.%s' %
> (lib_name, ext2))
>             if os.access(lib_path, os.R_OK):
>                 syb_libs.append(lib_name)
>                 break
> 
>> Could you please send me privately the list of files installed by your
>> freetds package or the result of the following command:
>>
>> ls /usr/lib/lib*blk* /usr/lib/lib*ct*  /usr/lib/lib*cs* \
>> /usr/lib/*libsybtcl* /usr/lib/lib*insck* /usr/lib/lib*comn* \
>> /usr/lib/lib*intl*
> 
> For interest sake:
> 
> $ ls /usr/lib/lib*blk* /usr/lib/lib*ct* /usr/lib/lib*cs*
> /usr/lib/lib*sybtcl* /usr/lib/lib*insck* /usr/lib/lib*comn*
> /usr/lib/lib*intl*
> ls: cannot access /usr/lib/lib*blk*: No such file or directory
> ls: cannot access /usr/lib/lib*sybtcl*: No such file or directory
> ls: cannot access /usr/lib/lib*insck*: No such file or directory
> ls: cannot access /usr/lib/lib*comn*: No such file or directory
> ls: cannot access /usr/lib/lib*intl*: No such file or directory
> /usr/lib/libct.a
> /usr/lib/libct.so.4
> /usr/lib/librpcsecgss.so.3.0.0
> /usr/lib/libct.la
> /usr/lib/libct.so.4.0.0
> /usr/lib/librpcsvc.a
> /usr/lib/libct.so
> /usr/lib/librpcsecgss.so.3
> 
> 
> Many thanks for your assistance.
> 
> 
> Warm regards,
> 
> Terry

Re: [Python-sybase-misc] "ImportError: .../sybasect.so: undefined symbol: cs_config"

[Terry B. <te...@te...>]

On Fri, Mar 6, 2009 at 1:25 PM, Sébastien Sablé
<sa...@us...> wrote:
> the sybase module is not linked to the freetds libraries, that is why there
> are some undefined symbols.
>
> This is probably because the setup.py script is not looking with the correct
> name for those libraries.

Hi Sébastien,

Absolutely correct, thanks.

Commenting out the lines that append _r64 to the lib path for 64-bit
arch fixes the problem:

if os.name == 'posix':                  # unix
   # Most people will define the location of their Sybase
   # installation in their environment.
...
   lib_names += ['sybblk', 'sybct', 'sybcs', 'sybtcl', 'sybinsck',
'sybcomn', 'sybintl', 'sybunic']
   for name in lib_names:
       extensions = [('', 'a'), ('', 'so'), ('_r', 'a'), ('_r', 'so')]
#        if have64bit and sys.platform not in ['osf1V5']:
#            extensions = [('_r64', 'a'), ('_r64', 'so')]
       for (ext1, ext2) in extensions:
           lib_name = "%s%s" % (name, ext1)
           lib_path = os.path.join(sybase, 'lib', 'lib%s.%s' %
(lib_name, ext2))
           if os.access(lib_path, os.R_OK):
               syb_libs.append(lib_name)
               break

> Could you please send me privately the list of files installed by your
> freetds package or the result of the following command:
>
> ls /usr/lib/lib*blk* /usr/lib/lib*ct*  /usr/lib/lib*cs* \
> /usr/lib/*libsybtcl* /usr/lib/lib*insck* /usr/lib/lib*comn* \
> /usr/lib/lib*intl*

For interest sake:

$ ls /usr/lib/lib*blk* /usr/lib/lib*ct* /usr/lib/lib*cs*
/usr/lib/lib*sybtcl* /usr/lib/lib*insck* /usr/lib/lib*comn*
/usr/lib/lib*intl*
ls: cannot access /usr/lib/lib*blk*: No such file or directory
ls: cannot access /usr/lib/lib*sybtcl*: No such file or directory
ls: cannot access /usr/lib/lib*insck*: No such file or directory
ls: cannot access /usr/lib/lib*comn*: No such file or directory
ls: cannot access /usr/lib/lib*intl*: No such file or directory
/usr/lib/libct.a
/usr/lib/libct.so.4
/usr/lib/librpcsecgss.so.3.0.0
/usr/lib/libct.la
/usr/lib/libct.so.4.0.0
/usr/lib/librpcsvc.a
/usr/lib/libct.so
/usr/lib/librpcsecgss.so.3


Many thanks for your assistance.


Warm regards,

Terry

Re: [Python-sybase-misc] "ImportError: .../sybasect.so: undefined symbol: cs_config"

[Sébastien S. <sa...@us...>]

Hi Terry,

the sybase module is not linked to the freetds libraries, that is why 
there are some undefined symbols.

This is probably because the setup.py script is not looking with the 
correct name for those libraries.

Could you please send me privately the list of files installed by your 
freetds package or the result of the following command:

ls /usr/lib/lib*blk* /usr/lib/lib*ct*  /usr/lib/lib*cs* \
/usr/lib/*libsybtcl* /usr/lib/lib*insck* /usr/lib/lib*comn* \
/usr/lib/lib*intl*

regards

--
Sébastien Sablé

Terry Burton a écrit :
> Hi,
> 
> I'm happily running the Python-Sybase module on Python 2.5.2, FreeTDS
> 0.82, Debian Lenny/686. Everything work with no problems.
> 
> However, when I build the module on an equivalent 64-bit system Python
> 2.5.2, FreeTDS 0.82, Debian Lenny/AMD64, I encounter the following
> runtime error when running import Sybase:
> 
> Traceback (most recent call last):
>   File "/srv/ipdb/bin/ndor_latest", line 3, in <module>
>     import Sybase
>   File "/usr/lib/python2.5/site-packages/Sybase.py", line 11, in <module>
>     from sybasect import *
> ImportError: /usr/lib/python2.5/site-packages/sybasect.so: undefined
> symbol: cs_config
> 
> Any clues as to what might be happening would be gratefully received.
> 
> 
> All the best,
> 
> Terry
> 
> 
> ----
> 
> Build output...
> 
> $ export SYBASE=/usr
> $ python setup.py build_ext -D HAVE_FREETDS -U WANT_BULKCOPY
> running build_ext
> building 'sybasect' extension
> creating build
> creating build/temp.linux-x86_64-2.5
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c blk.c -o
> build/temp.linux-x86_64-2.5/blk.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c databuf.c
> -o build/temp.linux-x86_64-2.5/databuf.o
> databuf.c:498: warning: initialization from incompatible pointer type
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c cmd.c -o
> build/temp.linux-x86_64-2.5/cmd.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c conn.c -o
> build/temp.linux-x86_64-2.5/conn.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c ctx.c -o
> build/temp.linux-x86_64-2.5/ctx.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c datafmt.c
> -o build/temp.linux-x86_64-2.5/datafmt.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c iodesc.c -o
> build/temp.linux-x86_64-2.5/iodesc.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c locale.c -o
> build/temp.linux-x86_64-2.5/locale.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c msgs.c -o
> build/temp.linux-x86_64-2.5/msgs.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c numeric.c
> -o build/temp.linux-x86_64-2.5/numeric.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c money.c -o
> build/temp.linux-x86_64-2.5/money.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c datetime.c
> -o build/temp.linux-x86_64-2.5/datetime.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c date.c -o
> build/temp.linux-x86_64-2.5/date.o
> gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fPIC -DWANT_BULKCOPY -DSYB_LP64 -DHAVE_DATETIME
> -DHAVE_DECIMAL -DHAVE_BLK_ALLOC -DHAVE_BLK_DESCRIBE -DHAVE_BLK_DROP
> -DHAVE_BLK_ROWXFER_MULT -DHAVE_BLK_TEXTXFER -DHAVE_CT_CURSOR
> -DHAVE_CT_DATA_INFO -DHAVE_CT_DYNAMIC -DHAVE_CT_SEND_DATA
> -DHAVE_CT_SETPARAM -DHAVE_CS_CALC -DHAVE_CS_CMP -DHAVE_FREETDS=1
> -UWANT_BULKCOPY -I/usr/include -I/usr/include/python2.5 -c sybasect.c
> -o build/temp.linux-x86_64-2.5/sybasect.o
> creating build/lib.linux-x86_64-2.5
> gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions
> build/temp.linux-x86_64-2.5/blk.o
> build/temp.linux-x86_64-2.5/databuf.o
> build/temp.linux-x86_64-2.5/cmd.o build/temp.linux-x86_64-2.5/conn.o
> build/temp.linux-x86_64-2.5/ctx.o
> build/temp.linux-x86_64-2.5/datafmt.o
> build/temp.linux-x86_64-2.5/iodesc.o
> build/temp.linux-x86_64-2.5/locale.o
> build/temp.linux-x86_64-2.5/msgs.o
> build/temp.linux-x86_64-2.5/numeric.o
> build/temp.linux-x86_64-2.5/money.o
> build/temp.linux-x86_64-2.5/datetime.o
> build/temp.linux-x86_64-2.5/date.o
> build/temp.linux-x86_64-2.5/sybasect.o -o
> build/lib.linux-x86_64-2.5/sybasect.so
> 
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> Python-sybase-misc mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/python-sybase-misc