Posts by jonathon@masto.ai
 (DIR) Post #AXTWsVCPiYlhg3L0Ma by jonathon@masto.ai
       2023-07-08T05:55:04Z
       
       0 likes, 0 repeats
       
       @simon I’d suggest being explicit about your build system in pyproject.toml; see https://setuptools.pypa.io/en/latest/userguide/pyproject_config.html (add the [build-system] block and specify setuptools as shown there).As for automatic discovery, setuptools is decently smart about detecting and handling common source layouts, or you can manually configure it similarly to how you would in setup.py (docs on this are in the linked page too).
       
 (DIR) Post #AXTYrwNhN04dbETZxI by jonathon@masto.ai
       2023-07-08T06:15:20Z
       
       0 likes, 0 repeats
       
       @simon If you leave it out, you’re at the mercy of pip or build to decide which build system gets used for you— and since that defines *all* of your build’s behavior, you probably want to be explicit here if you want reproducibility.
       
 (DIR) Post #AZD4NTciihVuv3Sy5g by jonathon@masto.ai
       2023-08-29T03:02:53Z
       
       0 likes, 0 repeats
       
       @mjg59 Context?If you're "just" looking for Unix sockets on Windows, modern Windows has them (or, at least, a subset) exposed through Winsock now (so, should be accessible through whatever Go's standard networking library is, at least in theory).If you're trying to communicate with a Cygwin-emulated Unix socket from outside Cygwin... that seems trickier. (They map into normal AF_INET sockets internally, but how that happens seems like it'd be getting uncomfortably close to Cygwin's guts.)