# Moving to third-party python library advantages and disadvantages

**URL:** <https://forum.inductiveautomation.com/t/moving-to-third-party-python-library-advantages-and-disadvantages/23958>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [April 9, 2019, 2:56pm UTC](https://forum.inductiveautomation.com/t/moving-to-third-party-python-library-advantages-and-disadvantages/23958 "2019-04-09T14:56:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![kcabatic](https://avatars.discourse-cdn.com/v4/letter/k/b19c9b/32.png) [@kcabatic](https://forum.inductiveautomation.com/u/kcabatic)\
**Post date:** [April 9, 2019, 2:56pm UTC](https://forum.inductiveautomation.com/t/moving-to-third-party-python-library-advantages-and-disadvantages/23958/1 "2019-04-09T14:56:37Z")

</div>

Hello,

We are planning to move our global scripts to ‘.py’ files to make maintenance easier and make use of a file versioning software. We are using 7.9 Ignition and do not plan on upgrading to 8.0 in the near future.

For those who had experience migrating to third-party ‘.py’ files what are the advantages and disadvantage?

One disadvantage I can imagine being able to deploy any updated .py files to other gateways. I do not remember seeing any functions in EAM to deploy the .py files only.

Thanks,

Ken