ansible 2.2.1.0 and Jinja2 2.9.5

[Michael Ströder]

HI!

When invoking ansible 2.2.1.0 with Python module Jinja2 2.9.5 installed it fails with:

ERROR! Unexpected Exception: The 'jinja2<2.9' distribution was not found and is required
by ansible

Are there really serious interop issues with Jinja 2.9.x+?

I'm asking because this blocks OS package updates for Jinja.

Ciao, Michael.

[Alan Orth]

Yeah, definitely issues between those two. See some issue reports on
GitHub, for example:

https://github.com/ansible/ansible/issues/20063

Regarads,

> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to ansible-proje...@googlegroups.com.
> To post to this group, send email to ansible...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/59040b07-7134-b5dd-1311-a424c6837c53%40stroeder.com.
> For more options, visit https://groups.google.com/d/optout.
>


--
Alan Orth
alan...@gmail.com
https://englishbulgaria.net
https://alaninkenya.org
https://mjanja.ch
"In heaven all the interesting people are missing." ―Friedrich Nietzsche
GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0

[Michael Ströder]

Alan Orth wrote:
> Yeah, definitely issues between those two. See some issue reports on
> GitHub, for example:
>
> https://github.com/ansible/ansible/issues/20063

Any news on that?

The bug above is labeled "affects_2.3" and there's no milestone defined yet.

I'm asking because the Linux distros ship with Jinja2 2.9.x and therefore their ansible
packages won't work.

Personally I'm using a virtualenv for ansible installation because of that. But what's
the general recommendation?

Ciao, Michael.

[Mirko Friedenhagen]

Hello Michael,

I would always recommend to take the virtualenv approach for non-trivial python software. The same principle is used for e.g. WARs or take a look at docker-compose, they even bundle Python itself. Wasting 30MB disk space is nothing compared to the effort needed to align every Python software on an OS in regards of their dependencies.

Regards
Mirko
--
Sent from my mobile

Ciao, Michael.

--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscribe@googlegroups.com.
To post to this group, send email to ansible-project@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/da0cf407-dad4-beb3-acc5-fd480c5d344a%40stroeder.com.

[Michael Ströder]

Mirko Friedenhagen wrote:
> I would always recommend to take the virtualenv approach for non-trivial python
> software.

In this particular case it's not a matter of whether to use virtualenv or not or whether
disk space is wasted. The real issue is the need for version pinning which eventually
leads to missing important security updates.

> The same principle is used for e.g. WARs or take a look at docker-compose, they even
> bundle Python itself. Wasting 30MB disk space is nothing compared to the effort needed
> to align every Python software on an OS in regards of their dependencies.

Yes, but same issues with how to install security updates there.

Ciao, Michael.