Tin Tvrtković
Tin Tvrtković
> Cron jobs are just normal jubs but with a job ID that includes the cron function name and the time That's how it works right now for unique cron...
Hello, I seem to be in the same boat. For example: https://coveralls.io/jobs/1532294 shows no files, and looking at the Travis log shows the coverage data was indeed generated.
`from pendulum import DateTime` works for me.
It works, I just consider it ugly and it exposes an implementation detail. I'm not really a fan of invalidation either (`del self.__dict__['cachable']`). `cached_property.iscached(self.cachable)`? `self.cachable.iscached` has some issues. (What if...
Hm, close. All of these terminate in a stdlib handler. It's also making the flow complex - the last diagram is `user -> structlog -> stdlib -> structlog -> stdlib`....
I am looking into this too. Could we emulate this with an autoscrolling ScrollView?
I see you folks are considering some pretty advanced stuff here. I was wondering if there was anything trio-specific in this, or could it be built as a separate library?...
Ah, I see. If it requires changes in the event loop itself, then implementing this in asyncio itself or uvloop might be a better strategy.
I would imagine it's an issue on their end. Does it also happens when you use `attrs.define` (as opposed to `attr`)?
There's https://peps.python.org/pep-0681/, which we do support both for `attr.s` and `define`.