PyCall doesn't expose PyObjects attributes to the Julia environment the same ways composite types expose their fields, leaving out many benefits of interactive development, making things difficult for beginners.
Perhaps it should be imperative to recast all PyObjects used in terms of Julian composite types, as well as methods that rely less on the python implementation.
The trade-off seems to be maintainability vs accessibility.
Attached is my independent experiment with implementing a WebDriver client in Julia using Requests.jl and JSON.jl, the only python dependency comes from initializing the browser session.
https://gist.github.com/NOTtheMessiah/b2d5f1128d07237446591c817bb1651e