Wheels again

Hi all,

I've hacked together some wheels for Windows at work and am wondering 
what the difficulty is to create wheels and publish them to pypi?

I can't reply to this thread, but have read it:
https://sourceforge.net/p/cx-oracle/mailman/message/32861443/

Anthony says:
 > The problem is that Oracle has a different ABI for Oracle 10, 11
 > and 12 but the Python wheel packaging format doesn't allow for
 > that concept

I don't fully understand the implications of that, but what I've done is:

     wheel convert cx_Oracle-5.1.3-12c.win32-py2.7.exe

And then a few lines of python that go into the created wheel and update 
the version in dir names, METADATA, metadata.json and RECORD from 5.1.3 
to 5.1.3+12c.

(I know this is a hacky way to do it, but easier than figuring out how 
to compile cx_Oracle on Windows)

Now, this seems to work for us, but, obviously it creates different 
versions of cx_Oracle for the same version number. Is that a problem 
though? I can't think of when you'd want cx_Oracle 11g and 12c installed 
in the same installation or virtualenv and am not sure that the current 
process allows that. Perhaps this won't work very well when using >= 
version specifications and a different versioning method might be needed?

One alternative to just having different versions is to have different 
packages - cx_Oracle_11g, cx_Oracle_12c.

Any thoughts on this? Am I missing some obvious problems with this? I 
certainly don't pretend to fully understand all ways in which cx_Oracle 
is used. It would be great to just have wheels for Windows, and I am 
willing to help however I can.

Cheers,

Adam

------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z