[issue15947] Assigning new values to instance of pointer types does not check validity

2020-08-30 Thread Facundo Batista
Facundo Batista added the comment: I'm closing this, it looks to me that behaviour changed and this is safe now. -- stage: -> resolved status: open -> closed ___ Python tracker

[issue15947] Assigning new values to instance of pointer types does not check validity

2019-04-26 Thread Mark Lawrence
Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue15947] Assigning new values to instance of pointer types does not check validity

2014-07-13 Thread Mark Lawrence
Mark Lawrence added the comment: @Facundo please accept our apologies for the delay in getting back to you. -- nosy: +BreamoreBoy, amaury.forgeotdarc, belopolsky, meador.inge versions: +Python 3.4, Python 3.5 -Python 3.2 ___ Python tracker

[issue15947] Assigning new values to instance of pointer types does not check validity

2012-09-15 Thread Facundo Batista
New submission from Facundo Batista: In the doc it says: Assigning a new value to instances of the pointer types c_char_p, c_wchar_p, and c_void_p changes the memory location they point to, not the contents of the memory block [...]. s = Hello, World c_s = c_wchar_p(s) print(c_s)