# setup module in 0.7 has Python 2.6 code in it… 0.7.1 pending

**URL:** <https://forum.ansible.com/t/setup-module-in-0-7-has-python-2-6-code-in-it-0-7-1-pending/11873>\
**Category:** Ansible Project\
**Created:** [September 8, 2012, 12:14pm UTC](https://forum.ansible.com/t/setup-module-in-0-7-has-python-2-6-code-in-it-0-7-1-pending/11873 "2012-09-08T12:14:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [September 8, 2012, 12:14pm UTC](https://forum.ansible.com/t/setup-module-in-0-7-has-python-2-6-code-in-it-0-7-1-pending/11873/1 "2012-09-08T12:14:00Z")

</div>

Hi all,

So the setup module contains a bit of Python 2.6-only code, which is not good on supporting older platforms that have only 2.4 … which is something we still want to support.  
It's important.

This isn't a problem for anyone who doesn't have any Python 2.4 infrastructure (like RHEL5), but if you do, it is.

We will probably do a minor 0.7.1 release and tar ball in the coming days.

To allow anyone to fix any bugs found on the release-0.7 branch, I'm not going to release this immediately, we'll probably shoot for early next week.

Everyone writing modules should make sure they only use Python 2.4 compatible code. This is usually something I review, though in this case it was string.format  
and it slipped through.

Thanks!

--Michael

---

<div class="post-metadata">

**Author:** ![Nigel\_Metheringham](https://avatars.discourse-cdn.com/v4/letter/n/3ec8ea/32.png) [@Nigel\_Metheringham](https://forum.ansible.com/u/Nigel_Metheringham)\
**Post date:** [September 10, 2012, 10:04am UTC](https://forum.ansible.com/t/setup-module-in-0-7-has-python-2-6-code-in-it-0-7-1-pending/11873/2 "2012-09-10T10:04:52Z")

</div>

Another trivial issue...

In the included rpm spec file:-  
&nbsp;&nbsp;- Date stamp for 0.7 has been copied from 0.6 (so is in August)  
&nbsp;&nbsp;- The changelog entries refer to a -0 release, but the spec  
&nbsp;&nbsp;&nbsp;&nbsp;uses a -1 release - ie the line should say:-

\* Thu Sep 6 2012 Michael DeHaan \<michael.dehaan@gmail.com\> - 0.7-1

&nbsp;&nbsp;Nigel.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [September 10, 2012, 12:01pm UTC](https://forum.ansible.com/t/setup-module-in-0-7-has-python-2-6-code-in-it-0-7-1-pending/11873/3 "2012-09-10T12:01:14Z")

</div>

Aha, you have discovered my perchant for time travel. I really  
should be more careful about covering that up.

You can send a pull request against the release-0.7 branch if you want.

(What is released is actually 0.7.0, FWIW, regardless of changelog)
