Hi,
I am building my python ibm_db driver on python 3.7 using the setup.py under https://github.com/SabaKauser/python-ibmdb/blob/master/IBM_DB/ibm_db/setup.py with 2to3 compatibility as:

python setup.py build
and installing as:
python setup.py install

I have a python script that after installing has new empty line added for every line.

e.g:
my source:
   if database is None:
        raise InterfaceError("createdb expects a not None database name value")
    if (not isinstance(database, basestring)) | \
       (not isinstance(codeset, basestring)) | \
       (not isinstance(mode, basestring)):
        raise InterfaceError("Arguments sould be string or unicode")

The generated file under C:\Users\skauser\AppData\Local\Programs\Python\Python37\Lib\site-packages\ibm_db-2.0.9-py3.7-win-amd64.egg\ibm_db_dbi.py

   if database is None:

        raise InterfaceError("createdb expects a not None database name value")

    if (not isinstance(database, str)) | \

       (not isinstance(codeset, str)) | \

       (not isinstance(mode, str)):

        raise InterfaceError("Arguments sould be string or unicode")

As you can see, there is this new line that is throwing runtime error.
  File "c:\users\skauser\appdata\local\programs\python\python37\lib\site-packages\ibm_db-2.0.9-py3.7-win-amd64.egg\ibm_db_dbi.py", line 846

    ^
SyntaxError: invalid syntax

Could you please let me know how can I get rid of this behavior?

When I install the package using pip, I don't see this behavior.

Thanks!
Saba.

Did anyone get a chance to look at my case?

Thanks,
Saba.

I suspect that this may not be a cpython issue, in which case, it should be closed here as 'not-a-bug'.  I suggest that you present this on python-list and ask 'where is the bug most likely to be?'  You should get more readers there.

Could you please share the URL

@sabakauser You can find python-list mailing list here : https://mail.python.org/mailman/listinfo/python-list

Thanks  Karthikeyan!

Looks like a duplicate of #34108

Closing as duplicate.

@sabakauser: if you update to a recent Python 3.7 (anything more recent than 3.7.1 should be enough), you should find that this is fixed.

resolution: duplicate
stage: resolved