-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switch to own packaged version of pygtfs #15040
Conversation
FYI, this is needed because SQLAlchemy complains if you attempt to use the same connection across threads. Here's the PR. Thanks for handling this @andrey-git! |
@andrey-git In a fit of insomnia i've taken another look at this and have determined a way for us to use the mainline version of PyGTFS. The only issue is that the project uses
Got any ideas to work around this? I think it would be better in practice to use the mainline dep instead of our own fork but obviously this won't fly if we can't lock the dep to a specific commit. We could also just use the PyPI published version 0.1.3. There's been minimal changes since that tag was cut in April 2016. BTW, the change that allows this is to construct our own SQLite URL like |
We want to avoid non pypi dependencies. If you can make it work with existing pypi package - awesome! |
This is now the last non-pypi package. |
@robbiet480 Kind ping on this :) |
Hi! The frozen fork here checked against only one |
@soraxas Please don't use merged PRs as a place for discussion. Please create an issue, or, use one of our other channels. |
Description:
Switch to own packaged version of pygtfs
This is the diff by @robbiet480 : jarondl/pygtfs@master...robbiet480:fix-sqlite-multithreading
According to Robbie it is needed and was rejected upstream.
Related issue (if applicable): #7069