-
Notifications
You must be signed in to change notification settings - Fork 90
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
Bring jinjasql in-line with Jinja2 3.1.2 #53
base: master
Are you sure you want to change the base?
Conversation
@boris-tumbev any chance we can get this merged to main and then an official pip package built? |
@sripathikrishnan can we get a merge here plz |
@boris-tumbev @sripathikrishnan can this PR be merged please? |
If only i had the write access :D I need it too, but i guess @sripathikrishnan does not maintain the project :( |
maybe time to fork? |
* Update jinja requirements * Update Jinja requirements * Markupsafe moved and autoescape is built-in * Update version and relax requirements Co-authored-by: Jaco Stroebel <[email protected]>
It could probably use some more love on a maintained fork. |
@sripathikrishnan: Please merge this to avoid a forking of this project... |
Please merge this PR. Jinja < 3.X is well old by now, and this PR/branch is nice and clean. |
@sripathikrishnan - Could we get this PR approved? It'd be really useful. |
It will be helpful if this PR is merged and a new release is created for distribution 🙏 |
For what it is worth, I ended up vendoring in my changes to a local fork to use internally. I am fairly sure that this repository can be considered unmaintained. |
anyone have a more active fork? |
we are trying to maintain a fork here - for our personal and company projects |
No description provided.