Raj is a product manager at InterSystems focused on developer experience. He pioneered Web mapping-as-a-service in the late 1990s with Syncline, a startup he co-founded. After that he finished his PhD in Information Systems for Planning at MIT, creating a distributed computing architecture for urban information systems based on web services design patterns.
He then worked for a decade on spatial data interoperability challenges with the Open Geospatial Consortium helping governments work with software companies to share and manage geographic information for natural resource management, disaster relief, and defense coordination.
Prior to joining InterSystems, Raj worked in developer relations for database and data science cloud offerings at IBM.
The AI bot isn't paying attention to the Python part of the question?
Thanks for the question, @André Dienes Friedrich. The simple answer is no, there is no set expiration time. We like to keep deprecated features around as long as a good number of users are depending upon them in production. Some reasons why a feature would be removed are: keeping the deprecated library conflicts with important features of the replacement; it becomes too burdensome to support the deprecated one; or the deprecated one becomes a risk in terms of security or data integrity. That hasn't happened yet with the libraries you mention.
@Ronaldo Nascimento what kind of connection? DBAPI? Can you share a code sample?