Ilya Kulakov
Ilya Kulakov
TBH I'm behind current best practices for tracing. Perhaps those APIs were replaced with something new from Instruments.app?
@JanX2 Ah, When saw in my email I first thought about some edge-case key combination on rare locale with some mysterious input method :) Happy NYE!
> One of my main issues currently is that the new persistence format in defaults is different and I need to find a way to bridge the old format to...
Another workaround: Set the `RUSTC_WRAPPER` environment variable or the [`build.rustc-wrapper`](https://doc.rust-lang.org/cargo/reference/config.html#buildrustc-wrapper) Cargo config variable to point to a custom shell script: ```shell #!/bin/zsh target_option_idx=${@[(Ie)--target]} if [[ ${target_option_idx} -ne 0 ]]; then...
There are some private frameworks + Accounts.framework, Social.framework
The main benefit is to be able to integrate with various libraries that deal with user input such as CLI toolkits, config parsers, ORM etc. `urlparse` is too abstract to...
I would like to see how far it can / should be integrated into pyzmq. I think both `connect` and `bind` should be able to accept it, what about `last_endpoint`?
Perhaps both `Address` and `Endpoint` should subclass `UserString`? Current `__iter__` can be replaced with the `as_tuple` method.
@minrk Ok, but considering that, would it be better to have them as strings or objects?
UserString would allow to avoid any changes to pyzmq though. Which makes sense, as URL introspection does not make sense there. Not with current API.