opened
danizen
username_0
John,

I have this working now in my environment.   It works like a charm.   I have about 70 developers and more CRUD applications, and I don't want everyone of them needing to set the 'POOL' parameter.   Also, our QA and Production servers may not install from the web.   I typically build to a wheel file, which can then be distributed where needed.

If you want someone else to help maintain the package, this one doesn't seem hard to maintain.
Allow bdist_wheel, support Python 3.4/3.5, make 'POOL' optional
issue
created
JohnPapps
username_1
Thank you for your time with this.  

Having a sensible default for the POOL makes perfect sense.  I didn't really have enough opportunity to figure out what would be sensible, so your comments are useful and welcome.

I haven't had issues with the hyphens in the package name, so would be interested to know where this has been an issue for you.
comment
created
danizen
username_0
I went into python manage.py shell in one project and entered `import django-oracle-drcp` and was told there was a syntax error.   In retrospect, I can see that `__import__ ("django-oracle-drcp")` would have worked, but this is ugly syntax.

While consistency is the bugaboo of small minds, there's always PEP8 - https://www.python.org/dev/peps/pep-0008/#package-and-module-names
comment
created
danizen
username_0
So, I'll make the changes you suggest and let's see.
comment
created
danizen
username_0
I'll test this on Monday, and maybe add a STATISTICS.md based on an email from work that compares CONN_MAX_AGE against Oracle DRCP.   The goal was to show that you are not giving up much performance by having a pool rather than dedicated per-process connections.
comment
created
danizen
username_0
I tested with modifications from last night, and it works.  I think this is ready to merge, but still welcome suggested changes.
comment