Re: [sqlalchemy] Proposal to discontinue pymssql in favor of pyodbc

2017-01-25 Thread Jonathan Vanasco 

On Wednesday, January 25, 2017 at 11:01:41 AM UTC-5, Randy Syring wrote:
>
>
>- pymssql has struggled to find maintainers who can devote time to it 
>and it is starting to languish.
>
>  Have you tried speaking with the "new" Microsoft?  Perhaps they'd be 
willing to contribute funds or engineers for a while.

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] Proposal to discontinue pymssql in favor of pyodbc

2017-01-25 Thread Randy Syring 

Mike,

While I have not done work recently committing to the project, I am one 
of the maintainers.  I'm an owner of the pymssql Github organization, 
pay for the pymssql.org domain, and try to generally keep up with things 
as time permits.


Regarding being an "active" project, that is debatable.  Ramiro has done 
great work over the past year, but we have generally been unable to 
maintain the project as it should be maintained.  We have important 
issues out there, like a request for a new release for code that is 
already in GitHub, but just don't have the manpower to make the 
release.  These issues could easily be addressed if we had someone who 
could devote their effort in that direction, but we don't and have 
historically struggled to have anything like consistent effort put 
towards maintaining/improving pymssql.  That's not a complaint, the work 
that has been done is appreciated, it's just what we face.


I'm not proposing that pymssql be discontinued _simply_ because another 
project exists.  I'm proposing that it be discontinued because:


 * Microsoft has come out in-favor of ODBC and pyodbc and, with their
   support, pyodbc could be a technically superior product.
 * If Microsoft is supporting pyodbc, many new users will start there
   and probably not even look for another solution (like pymssql).
 * pymssql has struggled to find maintainers who can devote time to it
   and it is starting to languish.

So, my thought is, if we don't bring anything to the table that pyodbc 
doesn't bring, then why shouldn't we point people in that direction instead.


However, I appreciate your input here and on the GH issue that pymssql 
is more stable than pyodbc.  That is exactly the kind of information I'm 
looking for.



*Randy Syring*
Chief Executive Developer
Direct: 502.276.0459
Office: 812.285.8766
Level 12 

On 01/25/2017 10:47 AM, mike bayer wrote:
I don't see how it's appropriate to even suggest that an open source 
project close its doors simply because another project exists.If 
you were the maintainer of pymssql, that would be one thing, but 
looking at the commits it seems to continue to be an active project.


pymssql handles our tests more cleanly than pyodbc which has constant 
datatype issues,  and I have had several non-response-situations from 
the maintainer on the pyodbc side in the somewhat distant past 
(whereas I've had great response with pymssql issues), so unless the 
situation has vastly changed I'd prefer pymssql continue its excellent 
work.



On 01/25/2017 10:24 AM, Randy Syring wrote:

There is a proposal open to discontinue pymssql development and point
people towards pyodbc.  Since pymssql is a documented backend for SA, I
figured there might be some people here who are interested.

If you have any skin in that game and want to comment, please visit the
issue: https://github.com/pymssql/pymssql/issues/477

Thanks.

--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and
Verifiable Example. See http://stackoverflow.com/help/mcve for a full
description.
---
You received this message because you are subscribed to the Google
Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sqlalchemy+unsubscr...@googlegroups.com
.
To post to this group, send email to sqlalchemy@googlegroups.com
.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.




--
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper


http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

Re: [sqlalchemy] Proposal to discontinue pymssql in favor of pyodbc

2017-01-25 Thread mike bayer 
I don't see how it's appropriate to even suggest that an open source 
project close its doors simply because another project exists.If you 
were the maintainer of pymssql, that would be one thing, but looking at 
the commits it seems to continue to be an active project.


pymssql handles our tests more cleanly than pyodbc which has constant 
datatype issues,  and I have had several non-response-situations from 
the maintainer on the pyodbc side in the somewhat distant past (whereas 
I've had great response with pymssql issues), so unless the situation 
has vastly changed I'd prefer pymssql continue its excellent work.



On 01/25/2017 10:24 AM, Randy Syring wrote:

There is a proposal open to discontinue pymssql development and point
people towards pyodbc.  Since pymssql is a documented backend for SA, I
figured there might be some people here who are interested.

If you have any skin in that game and want to comment, please visit the
issue: https://github.com/pymssql/pymssql/issues/477

Thanks.

--
SQLAlchemy -
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and
Verifiable Example. See http://stackoverflow.com/help/mcve for a full
description.
---
You received this message because you are subscribed to the Google
Groups "sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sqlalchemy+unsubscr...@googlegroups.com
.
To post to this group, send email to sqlalchemy@googlegroups.com
.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.


--
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper


http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups "sqlalchemy" group.

To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.

[sqlalchemy] Proposal to discontinue pymssql in favor of pyodbc

2017-01-25 Thread Randy Syring 
There is a proposal open to discontinue pymssql development and point 
people towards pyodbc.  Since pymssql is a documented backend for SA, I 
figured there might be some people here who are interested.

If you have any skin in that game and want to comment, please visit the 
issue: https://github.com/pymssql/pymssql/issues/477

Thanks.

-- 
SQLAlchemy - 
The Python SQL Toolkit and Object Relational Mapper

http://www.sqlalchemy.org/

To post example code, please provide an MCVE: Minimal, Complete, and Verifiable 
Example.  See  http://stackoverflow.com/help/mcve for a full description.
--- 
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sqlalchemy+unsubscr...@googlegroups.com.
To post to this group, send email to sqlalchemy@googlegroups.com.
Visit this group at https://groups.google.com/group/sqlalchemy.
For more options, visit https://groups.google.com/d/optout.