# How to specify explicit version requirements for external module

**URL:** <https://forum.ansible.com/t/how-to-specify-explicit-version-requirements-for-external-module/21659>\
**Category:** Ansible Developer\
**Tags:** ansible-devel\
**Created:** [June 3, 2016, 2:12pm UTC](https://forum.ansible.com/t/how-to-specify-explicit-version-requirements-for-external-module/21659 "2016-06-03T14:12:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\
**Post date:** [June 3, 2016, 2:12pm UTC](https://forum.ansible.com/t/how-to-specify-explicit-version-requirements-for-external-module/21659/1 "2016-06-03T14:12:43Z")

</div>

Either is fine, currently this is only for display, so whatever conveys the message.

We might change this in the future as we automate validation of requirements.

---

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [June 3, 2016, 3:13pm UTC](https://forum.ansible.com/t/how-to-specify-explicit-version-requirements-for-external-module/21659/2 "2016-06-03T15:13:00Z")

</div>

This might be something to bring up for standardization. I’d like to see us stick with the python requirements spec.

On a slightly different note, I’m not sure how I feel about a module listing a requirement of a release candidate of a package.