Re: Getting Directory of Command Line Entry Point For Packages

> On 13 Nov 2021, at 06:26, Abdur-Rahmaan Janhangeer > wrote: > > Only thing is that os.getcwd is giving the path of site-packages and not > the directory from > which the command is run from. In which case the code is doing a os.chdir() before the call to os.getwd(). You need to call getwd(

Re: Unable to compile my C Extension on Windows: unresolved external link errors

> On 12 Nov 2021, at 22:53, Marco Sulla wrote: > > It seems that on Windows it doesn't find python3.lib, > even if I put it in the path. So I get the `unresolved external link` > errors. I think you need the python310.lib (not sure of file name) to get to the internal symbols. You can use t

Re: Unable to compile my C Extension on Windows: unresolved external link errors

> On 13 Nov 2021, at 09:00, Barry wrote: > > > >> On 12 Nov 2021, at 22:53, Marco Sulla wrote: >> >> It seems that on Windows it doesn't find python3.lib, >> even if I put it in the path. So I get the `unresolved external link` >> errors. > > I think you need the python310.lib (not sure o

Re: Getting Directory of Command Line Entry Point For Packages

Greetings, This is what I am trying to do: How to get the getcwd of the directory of where the command is run and not that of the file where the cli entrypoint is found. Having the user enter the absolute path as a cli argument does not sound nice. Kind Regards, Abdur-Rahmaan Janhangeer about

Re: Unable to compile my C Extension on Windows: unresolved external link errors

. Sorry, the problem is I downloaded the 32 bit version of VS compiler and 64 bit version of Python.. On Sat, 13 Nov 2021 at 11:10, Barry Scott wrote: > > > > > On 13 Nov 2021, at 09:00, Barry wrote: > > > > > > > >> On 12 Nov 2021, at 22:53, Marco Sulla wrote: > >> > >> It seems that o

Re: Getting Directory of Command Line Entry Point For Packages

On 13/11/21 7:23 pm, Abdur-Rahmaan Janhangeer wrote: os.getcwd is giving the path of site-packages and not the directory from which the command is run from. Something must be changing the working directory before getcwd is called. Once that happens there's no way I know of to find out what it w

Re: Avoid nested SIGINT handling

On Thu, 11 Nov 2021 17:22:15 +1100, Chris Angelico wrote: > Threads aren't the point here - signals happen immediately. Actually, signals are not delivered immediately. Signals are delivered the next time the process gets its turn on CPU. The process scheduler will make process runnable and the

Re: Avoid nested SIGINT handling

On Sun, Nov 14, 2021 at 4:42 AM Mladen Gogala via Python-list wrote: > > On Thu, 11 Nov 2021 17:22:15 +1100, Chris Angelico wrote: > > > Threads aren't the point here - signals happen immediately. > > Actually, signals are not delivered immediately. Signals are delivered > the next time the proces

Re: Avoid nested SIGINT handling

On 11/12/21, Mladen Gogala via Python-list wrote: > On Thu, 11 Nov 2021 17:22:15 +1100, Chris Angelico wrote: > >> Threads aren't the point here - signals happen immediately. > > [snip: description of POSIX signals] > > BTW, that's the case on both Unix/Linux systems and Windows systems. Windows