# Best-effort deserialize a \`.jls\` file

**URL:** https://discourse.julialang.org/t/best-effort-deserialize-a-jls-file/111845
**Category:** General Usage
**Created:** [March 19, 2024, 9:57pm UTC](https://discourse.julialang.org/t/best-effort-deserialize-a-jls-file/111845 "2024-03-19T21:57:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![goretkin](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/goretkin/32/167_2.png) [@goretkin](https://discourse.julialang.org/u/goretkin)
#### Post date: [March 19, 2024, 9:57pm UTC](https://discourse.julialang.org/t/best-effort-deserialize-a-jls-file/111845/1 "2024-03-19T21:57:44Z")

</div>

I am trying a workaround for precompiling code that is used via `PythonCall.jl`, involving serializing many method instances in one pass, and precompiling them in another, and serializing the `MethodInstance` values in between. On deserialization, I am seeing

`UndefVarError: #pytuple_fromiter not defined` . Is there a way to do a best-effort deserialization to skip over problematic values?
