Kyle Altendorf comments

Results 572 comments of


                                            Kyle Altendorf

creating/binding a socket in a fixture causes it to not close

Forcing it to run `wrapped_function()` instead of `prof()` seems to avoid the problem. So, perhaps I need to bump this over there. I'll see if I can make a recreation...

creating/binding a socket in a fixture causes it to not close

It does appear to be down in `memory_profiler` (or below?). https://github.com/pythonprofilers/memory_profiler/issues/342 I would personally leave this open until it is resolved so it is easy to find if anyone else...

creating/binding a socket in a fixture causes it to not close

Already filed a bug there since I could recreate with just it. Link above. I'll follow up there if I manage any more debugging.

Unknown Excluded in sublists

Seems like the `marshmallow.EXCLUDE` is being applied only to the top level schema and isn't cascaded down. I can imagine sometimes wanting it to cascade (such as your case probably)...

Unknown Excluded in sublists

Hmm, I guess in the granular case it could be per attribute's usage of a class/schema? A pure marshmallow line for `not_yet_known: List[Ambiguous]` would look something like `not_yet_known = marshmallow.fields.List(AmbiguousSchema(unknown=marshmallow.EXCLUDE))`....

Unknown Excluded in sublists

I guess it might be: ```python not_yet_known: List[Ambiguous] = desert.ib( marshmallow_field=marshmallow.fields.List( desert.schema(cls=Ambiguous, meta={'exclude': marshmallow.EXCLUDE}) ) ) ```

Unknown Excluded in sublists

If you need that a lot you can for now compensate with a helper function. ```python def my_excluding_ib(cls): return desert.ib( marshmallow_field=marshmallow.fields.List( desert.schema(cls=cls, meta={'exclude': marshmallow.EXCLUDE}) ) ) not_yet_known: List[Ambiguous] = my_excluding_ib(cls=Ambiguous)...