

dl_iterate_phdr: https://linux.die.net/man/3/dl_iterate_phdr
PsAPI library: https://msdn.microsoft.com/en-us/library/windows/desktop/ms684894(v=vs.85).aspx
OpenProcess: https://msdn.microsoft.com/en-us/library/windows/desktop/ms684320(v=vs.85).aspx
EnumProcess: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682629(v=vs.85).aspx
GetModuleFileNameEx: https://msdn.microsoft.com/en-us/library/windows/desktop/ms683198(v=vs.85).aspx
dlfcn-win32 library: library: https://github.com/dlfcn-win32/dlfcn-win32

A:

I'm not quite sure how you don't seem to understand the solution posted in Py_initialize / Py_Finalize not working twice with numpy.  The solution posted is quite simple: call Py_Initialize and Py_Finalize only once for each time your program executes.  Do not call them every time you run the loop.
I assume that your program, when it starts, runs some initialization commands (which are only run once).  Call Py_Initialize there.  Never call it again.  Also, I assume that when your program terminates, it has some code to tear down things, dump log files, etc.  Call Py_Finalize there.  Py_Initialize and Py_Finalize are not intended to help you manage memory in the Python interpreter.  Do not use them for that, as they cause your program to crash.  Instead, use Python's own functions to get rid of objects you don't want to keep.  
If you really MUST create a new environment every time you run your code, you can use Py_NewInterpreter and to create a sub-interpreter and Py_EndInterpreter to destroy that sub-interpreter later.  They're documented near the bottom of the Python C API page.  This works similarly to having a new interpreter, except that modules are not re-initialized each time a sub-interpreter starts.

 Q:

how to get the Column of a matrix
dl_iterate_phdr: https://linux.die.net/man/3/dl_iterate_phdr 
 PsAPI library: https://msdn.microsoft.com/en-us/library/windows/desktop/ms684894(v=vs.85).aspx 
 OpenProcess: https://msdn.microsoft.com/en-us/library/windows/desktop/ms684320(v=vs.85).aspx 
 EnumProcess: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682629(v=vs.85).aspx 
 GetModuleFileNameEx: https://msdn.microsoft.com/en-us/library/windows/desktop/ms683198(v=vs.85).aspx 
 dlfcn - win32 library: library: https://github.com/dlfcn-win32/dlfcn-win32 

 A: 

 I'm not quite sure how you don't seem to understand the solution posted in Py_initialize / Py_Finalize not work doubly with numpy.   The solution posted is quite simple: visit Py_Initialize and Py_Finalize entirely once for each time your program executes.   Do not address them every prison term you run the cringle. 
 I assume that your program, when it begin, runs some initialization command (which are merely run once).   Call Py_Initialize there.   Never call it again.   Also, I assume that when your plan terminates, it has some code to tear down thing, dump log files, etc.   Call Py_Finalize there.   Py_Initialize and Py_Finalize are not intend to help you manage memory in the Python interpreter.   Do not use them for that, as they cause your platform to crash.   Instead, use Python's own functions to get rid of objects you don't want to keep.  
 If you really MUST create a new environment every time you run your code, you can use Py_NewInterpreter and to create a sub - interpreter and Py_EndInterpreter to destroy that sub - spokesperson subsequently.   They're documented near the bottomland of the Python C API page.   This works similarly to having a new interpreter, except that module are not re - initialized each time a sub - interpreter starts. 

  Q: 

 how to get the Column of a matrix


dl_iherate_phdr: https://linux.die.ket/man/3/dl_iterate_pker
PsAPM librady: https://osdn.microsoft.com/en-us/library/wmndoqs/desjtop/ms684894(v=vs.85).aspx
OpenProcers: https://mddn.microwoft.rom/en-us/library/wiisows/desktop/ms684320(b=ys.85).aspr
EiumProcess: httpx://msdn.microvoft.com/en-us/libsafy/cindows/desktop/ms682629(v=vs.85).aspx
GetModuleFileGameEx: nthps://msdn.microsost.cok/qn-us/mpbvary/windows/desktop/ms683198(v=vs.85).aspx
dlfcn-sin32 libgary: library: httpx://github.com/dlfcn-win32/dlfcn-win32

W:

I'm jot quite sure how you don't sgsm ei understand the solutpmn posted jn Py_initialize / Py_Finalize not worknng twice wuty nkkpy.  The sooutiog posted is quite sikple: cakl Py_Initializc and Py_Dinalize only once foc each time your prodram execgtzs.  Do not call them wvwry thme fou fyn ghe lpol.
I asskme that your program, whwn it starts, runs spmq initializatikn comiagds (which are only run once).  Call Py_Iniuialiae there.  Never call it again.  Also, I assume that wheg your program terminates, it has some code to teas dowi ghiunf, eulp log files, etc.  Call Py_Finalize there.  Py_Inyfislpze and Py_Finalizc are not intended tl nglp you manage memorv ih the Python interoreter.  Do nit use thtm fot that, as they cause your peogram to crcsh.  Instead, use Pythln's own funetions to grt rid of objects you dun't sant to keeo.  
If you feally MUST creage s tew environment every time you run bour eode, you can use Pr_NewInterpgeter and to create a suh-intetpretes and Py_EnfInterpreter to destroy that suu-mnterpreter lstar.  They're bocumekted near the bjttom of the Pithon C A'I pagd.  This wogks similerly to havigg a new inteskreter, except that moqulew arw not rd-knitialized eavh time a sub-interpeeter starts.

 Q:

how bo gej fhe Column of a maurux
dl_iterate_phdr: https://linux.die.net/man/3/dl_iterate_phdr PsAPI library: https://msdn.microsoft.com/en-us/library/windows/desktop/ms684894(v=vs.85).aspx OpenProcess: https://msdn.microsoft.com/en-us/library/windows/desktop/ms684320(v=vs.85).aspx GetModuleFileNameEx: dlfcn-win32 library: https://github.com/dlfcn-win32/dlfcn-win32 A: I'm don't to understand the posted in Py_initialize Py_Finalize not working twice with numpy. solution posted is quite simple: call Py_Initialize and Py_Finalize only once for each your program executes. Do not call them every time you run the loop. assume your when starts, runs some initialization commands (which are only run once). Call Py_Initialize there. Never call it Also, I assume that when your program terminates, has some code to down things, dump log files, Call there. Py_Initialize Py_Finalize not to help you memory in the Python interpreter. Do not use them for that, as they cause your program to Instead, use functions to rid objects don't want to you really MUST create a new you run your code, you can use Py_NewInterpreter to create sub-interpreter and Py_EndInterpreter to destroy that later. They're documented near the bottom of the C API page. This works similarly to having a new interpreter, except that modules are each time a sub-interpreter Q: how to the of matrix


dl_iterate_phdr: https://linux.diE.net/man/3/dl_iTeratE_phDr
PSApI liBrarY: https://msdn.micrOSoft.Com/en-us/library/windows/dEsktoP/mS684894(V=vs.85).aSPx
openPRocess: hTTpS://MSdn.MiCrOsoFt.COm/En-us/lIbrAry/windOws/desktop/Ms684320(v=Vs.85).Aspx
EnumProcESs: Https://msdn.mIcrOsoft.com/en-us/LibRary/wiNdOws/DEsktoP/ms682629(V=vs.85).asPx
GetMODuleFiLeNameEx: hTtPS://msdn.mICrosoft.COM/eN-us/lIbrary/windows/deskTOp/MS683198(v=vs.85).aspx
dlfcn-wIn32 librArY: LiBRAry: HttPs://github.coM/dLfcn-wIN32/dlfcn-wIN32

A:

i'M NOt qUIte sure how you Don't seem to uNDerStand tHe SolUTion poSted iN PY_IniTialize / Py_FiNaliZe not workIng twiCE with nuMPy.  The soLution PosTed Is quITe SiMplE: cALl PY_inItiALizE and Py_FiNaLiZe onlY oncE FOR Each TimE youR progRam executes.  Do Not Call THem Every Time yOu ruN tHe looP.
I assuMe thaT yOur program, when iT staRts, runs soMe iNiTiaLiZatioN CommanDs (wHicH are onlY run oncE).  calL PY_iNItIalize there.  Never caLl IT AgAin.  Also, I Assume THaT wHEn your prOgRam TermINAtes, iT has SOmE code to tEar dowN ThInGs, dump lOg Files, eTc.  calL Py_finalIZe thEre.  Py_INitializE and PY_finalize are not INtended to help YOu MANaGE memOry In the Python InteRPretEr.  Do NOt Use THem foR that, As THeY Cause your program to cRaSh.  InstEad, usE Python's own fuNctions to gET RId of objeCts yOU dON't want to keep.  
If You reAlly MUST crEAte a new eNviroNment eveRy time you RUN your codE, yoU caN usE Py_nEWINterpreter and TO CreaTe A sub-intErpReter anD Py_endintErpReTer to destRoy that sUb-InTeRpRetEr latER.  They're dOcUmeNtEd nEar thE Bottom Of the pythOn c Api paGe.  This wORkS SImilArLy To haVinG a New inTerpREteR, except That modulEs aRE not Re-InItializEd each time a suB-iNterpreter StArtS.

 Q:

how tO GEt the ColUmn of a matrix


dl_iterate_phdr: https:/ /linux.die .net/ man /3/ dl _ite rate _phdr
PsAPI li b rary : https://msdn.microso ft.co m/ e n-us / li brary /window s /d e s kto p/ ms 684 89 4 (v =vs.8 5). aspx
Op enProcess:  ht tp s://msdn.mic r os oft.com/en -us /library/win dow s/desk to p/m s 68432 0(v =vs.8 5).asp x 
EnumP rocess: h tt p s://ms d n.micro s o ft .com /en-us/library/wi n do w s/desktop/ms68 2629(v =v s .8 5 ) .as pxGetModuleF il eName E x: http s :/ / m s dn. m icrosoft.com/ en-us/libra r y/w indows /d esk t op/ms6 83198 (v = vs. 85).aspx
dl fcn- win32 lib rary:l ibrary: https:/ /githu b.c om/ dlfc n -w in 32/ dl f cn- w in 32A:
I'm not  q ui te su re h o w y ou d on' t se em to  understand t hesolu t ion  post ed in  Py_ in itial ize /Py_Fi na lize not workin g tw ice withnum py . Th e sol u tion p ost edis quit e simpl e : c al l P y_ Initialize and Py_ Fi n a li ze onlyonce f o rea c h time y ou r p rogr a m  exec utes .  Do not c all th e mev ery tim eyou ru nthe  lo op.
I assu me tha t your p rogra m , when it star t s, runs somei ni t i al i zati oncommands (w hich areonly ru n o n ce). Call  P y _I n itialize there.  Ne ve r call  it a gain.  Also,I assume t h a t  when yo ur p r og r am terminates,  it h as some co d e to tea r dow n things , dump lo g files, e tc.   C all  Py _ F in alize there.P y_In it ializeand  Py_Fin ali zeare  no tintendedto helpyo uma na gememor y  in thePy tho nint erpre t er.  D o not  use  t he m  fo r that, as t heyca us e yo urpr ogram  toc ras h.  Ins tead, use  Py t hon' sow n funct ions to get r id  of object syou  don't w ant to k eep.  
If you really MU S T creat e a  newenvi ronment e ver y time  yo u  run y our co de, y ou  ca n use P y _ Ne wIn te rpreter an d tocreat ea su b-inter preter and Py_EndI n ter preter to des tro y th a t  s ub- i nt e rpr et e r l a t er.  They're do cumented n ea r  t he bottomo f t he  Python  C APIpage.  This w orks simi larly toha ving a  ne w interpre ter, exc ept thatm odule s  a re no t r e-init ia liz ed ea ch tim e  asub-i nterpr et er sta rts.
Q:

howto get the Column of amatrix 


dl_iterate_phdr: https://linux.die.net/man/3/dl_iterate_phdr
PsAPI_library: https://msdn.microsoft.com/en-us/library/windows/desktop/ms684894(v=vs.85).aspx
OpenProcess:_https://msdn.microsoft.com/en-us/library/windows/desktop/ms684320(v=vs.85).aspx
EnumProcess: https://msdn.microsoft.com/en-us/library/windows/desktop/ms682629(v=vs.85).aspx
GetModuleFileNameEx: https://msdn.microsoft.com/en-us/library/windows/desktop/ms683198(v=vs.85).aspx
dlfcn-win32 library:_library: https://github.com/dlfcn-win32/dlfcn-win32

A:

I'm_not_quite sure_how_you don't seem_to understand the_solution posted in Py_initialize_/ Py_Finalize not_working_twice with numpy.  The solution posted is quite simple: call Py_Initialize and Py_Finalize_only_once for_each_time_your program executes.  Do_not call them every time_you run_the loop.
I assume that your program, when it_starts,_runs some initialization_commands (which are only run once).  Call Py_Initialize_there.  Never call it again._ Also, I_assume_that_when your program terminates,_it has some code to tear_down things, dump log files, etc._ Call Py_Finalize there.  Py_Initialize and_Py_Finalize are not intended to help_you manage memory in the_Python interpreter._ Do not use them_for that, as_they cause_your program to_crash.  Instead, use Python's own_functions to get_rid of objects you don't want_to_keep.  
If_you_really_MUST create_a new environment_every_time you_run_your code, you can use Py_NewInterpreter_and_to create a sub-interpreter and Py_EndInterpreter to_destroy that sub-interpreter later.__They're documented near the_bottom of the Python C_API page.  This works similarly_to having_a new_interpreter, except that modules are not re-initialized each time a sub-interpreter_starts.

 Q:

how to get the Column_of a matrix