# Pycall in production?

**URL:** https://discourse.julialang.org/t/pycall-in-production/783
**Category:** General Usage
**Tags:** pycall
**Created:** [December 7, 2016, 4:43pm UTC](https://discourse.julialang.org/t/pycall-in-production/783 "2016-12-07T16:43:59Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Tem\_Pl](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@Tem\_Pl](https://discourse.julialang.org/u/Tem_Pl)
#### Post date: [December 7, 2016, 4:43pm UTC](https://discourse.julialang.org/t/pycall-in-production/783/1 "2016-12-07T16:43:59Z")

</div>

Does anyone have experience using PyCall in production? Is it reliable for long running applications?

---

<div class="post-metadata">

### Author: ![Ken-B](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ken-b/32/1780_2.png) [@Ken-B](https://discourse.julialang.org/u/Ken-B)
#### Post date: [December 8, 2016, 1:05pm UTC](https://discourse.julialang.org/t/pycall-in-production/783/2 "2016-12-08T13:05:36Z")

</div>

Yes, I’ve been running pycall for pyodbc as the julia odbc package had an issue at the time. It’s been running live for over a year now on a Windows server for an analytics backed to a web service. Only upgraded from 0.3 to 0.4 when that came out and never had an issue.

Cheers