Closed bwgref closed 1 year ago
For now, forcing regions==0.5 in requirements.txt until I figure out what changed in the metadata. #94
Hi Brian,
I also faced a problem with the new version of the region package. I noticed that the metadata 'include' returns 1 and not True.
I tried implementing a solution that doesn't break the code for regions version 0.5
for ri in reg: assert ri.meta['include'] == 1 or ri.meta['include'] is True, \ f'\n {regfile} has an exclusion region first! \n Put the source region first instead!' break
If it works I can create a PR, but since it is one line of code you can also change it directly. Let me know what you think.
Gullo
@mgullik I think there are more API changes in regions that were causing problems...have you made these local changes and made sure it all works?
Closed in #112
Hi @bwgref,
sorry I couldn't answer before. I saw you changed the assert to check the region. I think it should work now.
Seems to be some issues using regions 0.6 with some meta data when doing the region checking.