# Instances are renamed every time in MyHDL 0.10

**URL:** https://discourse.myhdl.org/t/instances-are-renamed-every-time-in-myhdl-0-10/272
**Category:** Bug
**Created:** [April 16, 2018, 12:11pm UTC](https://discourse.myhdl.org/t/instances-are-renamed-every-time-in-myhdl-0-10/272 "2018-04-16T12:11:19Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![mhavu](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.myhdl.org/mhavu/32/86_2.png) [@mhavu](https://discourse.myhdl.org/u/mhavu)
#### Post date: [April 16, 2018, 12:11pm UTC](https://discourse.myhdl.org/t/instances-are-renamed-every-time-in-myhdl-0-10/272/1 "2018-04-16T12:11:19Z")

</div>

I just upgraded to MyHDL 0.10 and the new API. This fixed a couple of issues I had, but also caused a new one: I get “_ToVHDLWarning: Previously used name being reused_” warnings every time I rerun conversion. In simulation, blocks are renamed on every run, so that it is necessary to manually add all signals in GTKWave on every iteration. With the code in thread [Instance-specific constants in VHDL conversion](http://discourse.myhdl.org/t/instance-specific-constants-in-vhdl-conversion/262/17), the first run gives me `biquad0_0`, `biquad1_0`, and `biquad2_0`. After five reruns, the blocks are named `biquad0_0_1_2_3_4_5`, `biquad1_0_1_2_3_4_5`, and `biquad2_0_1_2_3_4_5`.

EDIT: Apparently this has something to do with IPython.

---

_[View the full topic](https://discourse.myhdl.org/t/instances-are-renamed-every-time-in-myhdl-0-10/272)._