may be it is a bug for GdsLibrary.new_cell() about gdspy

[heitzmann]

@mujingfatasy This seems to be a problem with the global library maintained internally (used in early versions of gdspy).
You can try to set gdspy.library.use_current_library = False right after importing gdspy to fix the issue.

[mujingfatasy]

by the mean, the version of gdspy I used is 1.6.12

[tvt173]

yeah, I'd agree that seems to be a bug. it should be fixed though (and better practice) if you first instantiate a new library and add your cell to that, rather than using gdspy.current_library directly (which it seems you are doing)

for example

lib = gdspy.Library(name="mylibrary")
lib.new_cell(name)

[mujingfatasy]

OK, thanks a lot, but it seems that I was doing the same way as your recommendation，here is my source code :
lib=gdspy.GdsLibrary(name="stacked_balun")
turn1=lib.new_cell("turn1")
gdspy.current_library seems to be called by “ init ” function of Cell class which is called by lib.new_cell

[tvt173]

hmm, interesting. to be honest, i don't usually use the new_cell function. I would usually create the cell first then add it like lib.add(cell). I would give that a try. if you still get the problem, please share a reproducible example. or try submitting a patch. please by aware that you shouldn't add a cell with the same name twice, due to limitations of the GDSII format.

and if you are just getting started with gdspy, i would consider trying gdstk instead, the successor to this project

[mujingfatasy]

OK，thanks a lot