Jerry Ling

both of these can be sidestepped by selectively importing identifiers into namespace (e.g., `using BitIntegers: ...`), or re-exporting things from user module: ```julia module UserModule using BitIntegers: Int256 export Int256...

>As you can see, the last value still displays BitIntegers.Int256 right, and I guess the question is why does it matter what it displays? Is there any execution/practical implications?

>Which problems do you see mostly it's gonna be a breaking change, that's all, it's a social friction nto a technical one

because this error happened inside PythonCall, since after: ``` CondaPkg Found dependencies: /home/jiling/.julia/environments/BjetTLA/CondaPkg.toml ``` we're still in PythonCall's code yes, didn't work. `Pkg.resolve / update` don't think there's anything to...

What solved my issue was I need to manually call: ``` CondaPkg.resolve() ``` and it will install a bunch of stuff, and then somehow, `using PythonCall` no longer errors

example file would be great

@tamasgal because he recently refactored those code. From what I can tell, it's not a new issue, but the error message is now obscure, before `0.10.2`, I see ```julia julia>...

idk why Geant4 would write out files like that, I think they're including legacy metadata not used, a simple re-procesisng with `uproot` makes the data readable: ```python In [18]: import...

https://github.com/root-project/root/blame/a7877eefc02780b9ae3e3b56c9a4e5a22d58aa93/base/inc/TAttMarker.h#L55 https://github.com/root-project/root/blame/9394e091ba1097ecb85aa0551e4853db1e73088c/core/base/inc/TAttMarker.h#L56 this is the change from 1->2. Content-wise I don't see any difference tbh, so idk...

>but it's apparently using a TTree v5 and we only have support for more recent versions we can error on this if we can parse 0% of them