System information

0a061b6f9ea8ea10414e04a6a87c14c6b12ad04b

Operating system: Windows 7

Expected behavior

Dialog should be just info dialog (as it been before), not the error with ugly sound and big red sign.

Actual behavior

bi

Issue by westurner
Thursday Jul 19, 2018 at 20:39 GMT
Originally opened as dcowden/cadquery#287

https://pypi.org/project/cadquery/

https://github.com/pypa/readme_re

Proposed Behaviour

None of the core VPR algorithms should care if the relevant t_physical_tile is an input / output / IO type.

Current Behaviour

Some behavior is still dependent on whether a tile is an input / output / IO type.

Possible Solution

The relevant code shouldn't need to care. Once all callsites of is_input_type/is_output_type/is_io_type are removed, the

Are there any docs for the python bindings available. I have no idea how to use libredwg and run into a crash imediatly:

>>> import LibreDWG
>>> LibreDWG.Dwg_Data()
<LibreDWG.Dwg_Data; proxy of <Swig Object of type '_dwg_struct *' at 0x7f1dbf13d9c0> >
>>> data = LibreDWG.Dwg_Data()
>>> data.swig/python detected a memory leak of type 'BITCODE_MS *', no destructor found.
swig/python det