Skip to content
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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

ghost
Copy link

@ghost ghost commented Jul 11, 2022

No description provided.

@dmctavish
Copy link

@boris-tumbev any chance we can get this merged to main and then an official pip package built?

@dmctavish
Copy link

@sripathikrishnan can we get a merge here plz

@GBBBAS
Copy link

GBBBAS commented Oct 25, 2022

@boris-tumbev @sripathikrishnan can this PR be merged please?

@boris-tumbev
Copy link

If only i had the write access :D I need it too, but i guess @sripathikrishnan does not maintain the project :(

@dmctavish
Copy link

maybe time to fork?

pokle added a commit to pokle/jinjasql-poklet that referenced this pull request Oct 26, 2022
* 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]>
@ghost
Copy link
Author

ghost commented Oct 26, 2022

It could probably use some more love on a maintained fork.

@marhoy
Copy link

marhoy commented Dec 16, 2022

@sripathikrishnan: Please merge this to avoid a forking of this project...

@jlrobins
Copy link

Please merge this PR. Jinja < 3.X is well old by now, and this PR/branch is nice and clean.

@LewisCharlesBaker
Copy link

@sripathikrishnan - Could we get this PR approved? It'd be really useful.

@varadtupe
Copy link

It will be helpful if this PR is merged and a new release is created for distribution 🙏
It brought down Production Airflow on CloudCompose at my company when we upgraded it as Jinja2 was upgraded to 3.1.2

@ghost
Copy link
Author

ghost commented Feb 18, 2023

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.

@bitsofinfo
Copy link

anyone have a more active fork?

#55

@PandaWhoCodes
Copy link

we are trying to maintain a fork here -
https://github.com/pythonutilities/jinjasql

for our personal and company projects

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants