Brendan Molloy

This crate doesn't follow the appropriate idiom for how no_std is used in production in Rust projects. The pattern is to have a `std` feature, on by default. Here's some...

I'd note it's a separate issue from how the feature flags are specified. And given the extremely small amount of code using core2, would highly recommend dropping it.

I also support this use case. @sunli829: we make an API where the Query object will have different fields enabled or disabled depending on which customer we're building the API...

@sunli829 I'd like to take a shot at implementing this. Do you have a recommendation on where I should start looking inside the derives? 😄

Works as advertised. You are a wizard. :D

Hey! It is not yet something that exists, and I am aware of what other languages do. It's a neat feature, but I've always felt it... wasn't enough. My more...

It seems that this is specifically a limitation of hatchling: https://github.com/pypa/hatch/issues/279

Yeah, if it were possible. At least the banner area can be useful, for dictionary support, etc.

This is wonderful. Incidentally, there is a built-in mode in iOS where you can disable all third party keyboards, which is the _correct_ way to do secure keyboards, so in...

Can confirm the following worked on Windows: ``` def resource_callback(policy, resource): if type(resource) in ("PythonExtensionModule"): if resource.name == "_ctypes": resource.add_include = False ``` `extension_module_filter` does still run first though, and...