RA80533
RA80533
Has opinion changed on this at all? I see that in 2016 it was of the opinion that allowing this behavior would be better for defensive programming when dealing with...
Is that specific construct something you were going to add to the package? Is there anything I can do to help bring this feature to fruition?
I rebased the branch with the recent changes. Note the changes in [aa8d847](https://github.com/aio-libs/aioodbc/pull/429/commits/aa8d8476b4805b3934c394adef4a507be391183a); the commit contains the changes associated with the use of `asyncio.Future` that you recommended.
@mkleehammer What can I do to bring this over the finish line?
Node.js modules have to be imported using their full URLs in Deno (see [The `std/node` Library]). Change "child_process" to "https://deno.land/std/node/child_process.ts" and it should work. [The `std/node` Library]: https://deno.land/[email protected]/node/std_node
Could you elaborate on what you mean by unnecessary? Accessing `approximateTime.now` right now calls the function bound to its `get` attribute. There's already a function call.
@epoberezkin Is this actionable?
@brcrista Any word on this? Would anyone from the team be willing to review and possibly merge a PR fixing this behavior?