Mailman 3 June 2013 - Python-Dev

eval and triple quoted strings
by Walter Dörwald June 18, 2013

June 18, 2013

Hello all! This surprised me: >>> eval("'''\r\n'''") '\n' Where did the \r go? ast.literal_eval() has the same problem: >>> ast.literal_eval("'''\r\n'''") '\n' Is this a bug/worth fixing? Servus, Walter

9 23

Re: [Python-Dev] cpython: Issue #3329: Add new APIs to customize memory allocators
by Antoine Pitrou June 18, 2013

June 18, 2013

On Sat, 15 Jun 2013 00:44:11 +0200 (CEST) victor.stinner <python-checkins(a)python.org> wrote: > http://hg.python.org/cpython/rev/6661a8154eb3 > changeset: 84127:6661a8154eb3 > user: Victor Stinner <victor.stinner(a)gmail.com> > date: Sat Jun 15 00:37:46 2013 +0200 > summary: > Issue #3329: Add new APIs to customize memory allocators > > * Add a new PyMemAllocators structure > * New functions: > > - PyMem_RawMalloc(), PyMem_RawRealloc(), PyMem_RawFree(): GIL-free memory > allocator functions > - PyMem_GetRawAllocators(), PyMem_SetRawAllocators() > - PyMem_GetAllocators(), PyMem_SetAllocators() > - PyMem_SetupDebugHooks() > - _PyObject_GetArenaAllocators(), _PyObject_SetArenaAllocators() My two cents, but I would prefer if this whole changeset was reverted. I think it adds too much complexity in the memory allocation APIs, for a pretty specialized benefit. IMHO, we should be able to get by with less allocation APIs (why the new _Raw APIs) and less hook-setting functions. Regards Antoine.

5 20

Problem with pydoc script in PEP 405 venvs
by Vinay Sajip June 17, 2013

June 17, 2013

Issue #18224 (http://bugs.python.org/issue18224) highlights a problem on Windows with the pydoc script provided with venvs created by pyvenv. On POSIX, the script is named pydoc and causes no problems: on Windows, it is called pydoc.py and this causes problems because it shadows the stdlib pydoc module. Possible solutions: 1. Remove the pydoc script altogether from created venvs, on Windows but also on POSIX (for consistency). 2. Rename the pydoc script on both Windows and POSIX (e.g. to pydocs.py and pydocs respectively). 3. Rename the pydoc.py script to pydoc-script.py and introduce a simple .exe launcher pydoc.exe adjacent to it (which is how setuptools and distlib handle installed scripts). The first two approaches are backwards-incompatible, while the third is less likely to lead to breakage, but involves adding a Windows script launcher to Python. While this is a bigger change, I think any built-in Python installer functionality should include such a launcher (as setuptools and distlib do). Still, that's probably a discussion for another day. Does anyone have any comments? Approach #2 seems the most appropriate. I assume it would be reasonable to implement this in both 3.3 and 3.4, as it's not a change in core Python APIs. In the absence of adverse feedback here, I propose to implement approach #2 on both 3.3 and 3.4. Regards, Vinay Sajip

4 5

Writing Extensions for Python 3 in Windows
by Aditya Avinash June 17, 2013

June 17, 2013

Hi. This is the last place where I want to ask a question. I have searched for lots of tutorials and documentation on the web but, didn't find a decent one to develop extensions for Python 3 using a custom compiler (mingw32, nvcc). Please help me. PS: Don't point me to Python Documentation. It is not good for beginners. It doesn't elaborate about calls and implementation. -- Aditya Avinash Atluri

2 1

Backports galore
by Łukasz Langa June 16, 2013

June 16, 2013

Now we have (at least) the following libraries backported from 3.2+ to older versions of Python by members of the core team: - configparser - enum34 - singledispatch - subprocess32 - unittest2 There are also unofficial backports like billiard (multiprocessing). I would be happy if all those were more discoverable by the community at large. Having a single namespace for backports would be great but my spidey sense forebodes large flocks of bike sheds flying that way. Can we put links to those backports in the docs of older versions of Python? Most users would be better off using the updated packages while still deploying on an older release of Python. -- Best regards, Łukasz Langa WWW: http://lukasz.langa.pl/ Twitter: @llanga IRC: ambv on #python-dev

3 2

Clean way in python to test for None, empty, scalar, and list/ndarray? A prayer to the gods of Python
by Martin Schultz June 16, 2013

June 16, 2013

As much as I love python, the following drives me crazy, and I would wish that some future version would come up with a more consistent approach for this. And please don't reply with "Too bad if you don't know what type your data are..." - if I want to implement some generic functionality, I want to avoid constrains on the user where not absolutely necessary, and I believe this approach is truely pythonic. OK - here comes the problem set. These are in fact several related issues. Clearly, a solution exists for each of them, but you will have to admit that they are all very different in style and therefore unnecessarily complicate matters. If you want to write code which works under many circumstances, it will become quite convoluted. 1. Testing for None: From what I read elsewhere, the preferred solution is `if x is None` (or `if not x is None` in the opposite case). This is fine and it works for scalars, lists, sets, numpy ndarrays,... 2. Testing for empty lists or empty ndarrays: In principle, `len(x) == 0` will do the trick. **BUT** there are several caveats here: - `len(scalar)` raises a TypeError, so you will have to use try and except or find some other way of testing for a scalar value - `len(numpy.array(0))` (i.e. a scalar coded as numpy array) also raises a TypeError ("unsized object") - `len([[]])` returns a length of 1, which is somehow understandable, but - I would argue - perhaps not what one might expect initially Alternatively, numpy arrays have a size attribute, and `numpy.array([]).size`, `numpy.array(8.).size`, and `numpy.array([8.]).size` all return what you would expect. And even `numpy.array([[]]).size` gives you 0. Now, if I could convert everything to a numpy array, this might work. But have you ever tried to assign a list of mixed data types to a numpy array? `numpy.array(["a",1,[2,3],(888,9)])` will fail, even though the list inside is perfectly fine as a list. 3. Testing for scalar: Let's suppose we knew the number of non-empty elements, and this is 1. Then there are occasions when you want to know if you have in fact `6` or `[6]` as an answer (or maybe even `[[6]]`). Obviously, this question is also relevant for numpy arrays. For the latter, a combination of size and ndim can help. For other objects, I would be tempted to use something like `isiterable()`, however, this function doesn't exist, and there are numerous discussions how one could or should find out if an object is iterable - none of them truly intuitive. (and is it true that **every** iterable object is a descendant of collections.Iterable?) 4. Finding the number of elements in an object: From the discussion above, it is already clear that `len(x)` is not very robust for doing this. Just to mention another complication: `len("abcd")` returns 4, even though this is only one string. Of course this is correct, but it's a nuisance if you need to to find the number of elements of a list of strings and if it can happen that you have a scalar string instead of a 1-element list. And, believe me, such situations do occur! 5. Forcing a scalar to become a 1-element list: Unfortunately, `list(77)` throws an error, because 77 is not iterable. `numpy.array(77)` works, but - as we saw above - there will be no len defined for it. Simply writing `[x]` is dangerous, because if x is a list already, it will create `[[77]]`, which you generally don't want. Also, `numpy.array([x])` would create a 2D array if x is already a 1D array or a list. Often, it would be quite useful to know for sure that a function result is provided as a list, regardless of how many elements it contains (because then you can write `res[0]` without risking the danger to throw an exception). Does anyone have a good suggestion for this one? 6. Detecting None values in a list: This is just for completeness. I have seen solutions using `all` which solve this problem (see [question #1270920][1]). I haven't digged into them extensively, but I fear that these will also suffer from the above-mentioned issues if you don't know for sure if you are starting from a list, a numpy array, or a scalar. Enough complaining. Here comes my prayer to the python gods: **Please** - add a good `isiterable` function - add a `size` attribute to all objects (I wouldn't mind if this is None in case you don't really know how to define the size of something, but it would be good to have it, so that `anything.size` would never throw an error - add an `isscalar` function which would at least try to test if something is a scalar (meaning a single entity). Note that this might give different results compared to `isiterable`, because one would consider a scalar string as a scalar even though it is iterable. And if `isscalar` would throw exceptions in cases where it doesn't know what to do: fine - this can be easily captured. - enable the `len()` function for scalar variables such as integers or floats. I would tend to think that 1 is a natural answer to what the length of a number is. [1]: http://stackoverflow.com/questions/1270920/most-concise-way-to-check-whethe…

8 12

PEP 442 accepted
by Benjamin Peterson June 15, 2013

June 15, 2013

I (and Guido) are accepting PEP 442 (Safe object finalization) on the condition that finalizers are only ever called once globally. Congratulations to Antoine on writing yet another PEP that deeply touches the core language in a way that everyone can agree is an improvement.. I look forward to reviewing the code. -- Regards, Benjamin

3 5

Allow calling PyMem_Malloc() without the GIL held in Python 3.4
by Victor Stinner June 14, 2013

June 14, 2013

Hi, I would like to remove the "GIL must be held" restriction from PyMem_Malloc(). In my opinion, the restriction was motived by a bug in Python, bug fixed by the issue #3329. Let me explain why. The PyMem_Malloc() function is a thin wrapper to malloc(). It returns NULL if the size is lager than PY_SSIZE_T_MAX and have a well defined behaviour for PyMem_Malloc(0) (don't return NULL). So it is surprising to read in Include/pymem.h: "The GIL must be held when using these APIs." The reason is more surprising: in debug mode, PyMem_Malloc() is no more a thin wrapper to malloc(), but it calls internally PyObject_Malloc(), the "Python allocator" (called pymalloc). (Many other checks are done in debug mode, but it's unrelated to my point.) The problem is that PyObject_Malloc() is not thread-safe, the GIL must be held. Short history: fb45791150d1 (Mar 23 2002) "gives Python a debug-mode pymalloc" f294fdd18b5b (Mar 28 2002) removes the "check API family" e16dbf875303 (Apr 22 2002) redirects indirectly PyMem_Malloc() to PyObject_Malloc() in debug mode b6aff7a59803 (Sep 28 2009) reintroduces API checks So the GIL issue is almost as old as the debug mode for Python memory allocators. My patch attached to http://bugs.python.org/issue3329 changes the design of the debug memory allocators: they are now wrapper (hooks) on the underlying memory allocator (PyMem: malloc, PyObject: pymalloc), instead of always redirecting to pymalloc (ex: PyObject_Malloc). Using my patch, PyMem_Malloc() now always calls malloc(), even in debug mode. Removing the "GIL must be held" restriction is now safe. Do you agree? May it cause backward compatibility issue? PyMem_Malloc() and PyMem_MALLOC() call malloc(), except if the Python source code was manually modified. Does this use case concern many developers? Removing the GIL restriction would help to replace direct calls to malloc() with PyMem_Malloc(). Using PyMem_SetAllocators(), an application would be able to replace memory allocators, and these allocators would be used "everywhere". => see http://bugs.python.org/issue18203 Victor

2 2

Re: [Python-Dev] [Python-checkins] cpython: Closes issue 17947. Adds PEP-0435 (Enum, IntEnum) to the stdlib.
by Brett Cannon June 14, 2013

June 14, 2013

Ethan, did you forget to run ``hg add`` before committing? If not then why the heck did we argue over enums for so long if this was all it took to make everyone happy? =) On Fri, Jun 14, 2013 at 3:31 AM, ethan.furman <python-checkins(a)python.org>wrote: > http://hg.python.org/cpython/rev/fae92309c3be > changeset: 84117:fae92309c3be > parent: 84115:af27c661d4fb > user: Ethan Furman <ethan(a)stoneleaf.us> > date: Fri Jun 14 00:30:27 2013 -0700 > summary: > Closes issue 17947. Adds PEP-0435 (Enum, IntEnum) to the stdlib. > > files: > Doc/library/datatypes.rst | 1 + > 1 files changed, 1 insertions(+), 0 deletions(-) > > > diff --git a/Doc/library/datatypes.rst b/Doc/library/datatypes.rst > --- a/Doc/library/datatypes.rst > +++ b/Doc/library/datatypes.rst > @@ -30,3 +30,4 @@ > copy.rst > pprint.rst > reprlib.rst > + enum.rst > > -- > Repository URL: http://hg.python.org/cpython > > _______________________________________________ > Python-checkins mailing list > Python-checkins(a)python.org > http://mail.python.org/mailman/listinfo/python-checkins > >

1 0

Summary of Python tracker Issues
by Python tracker June 14, 2013

June 14, 2013

ACTIVITY SUMMARY (2013-06-07 - 2013-06-14) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open 4042 (+18) closed 25946 (+41) total 29988 (+59) Open issues with patches: 1795 Issues opened (41) ================== #17947: Code, test, and doc review for PEP-0435 Enum http://bugs.python.org/issue17947 reopened by ncoghlan #18159: ConfigParser getters not available on SectionProxy http://bugs.python.org/issue18159 opened by JBernardo #18161: call fchdir if subprocess.Popen(cwd=integer|fileobject) http://bugs.python.org/issue18161 opened by mmarkk #18162: Add index attribute to IndexError http://bugs.python.org/issue18162 opened by brett.cannon #18163: Add a 'key' attribute to KeyError http://bugs.python.org/issue18163 opened by brett.cannon #18164: Embedding Python doc incorrectly refers to LINKFORSHARED http://bugs.python.org/issue18164 opened by ned.deily #18165: Add 'unexpected_type' to TypeError http://bugs.python.org/issue18165 opened by brett.cannon #18166: 'value' attribute for ValueError http://bugs.python.org/issue18166 opened by brett.cannon #18167: cgi.FieldStorage fails to handle multipart/form-data when \r\n http://bugs.python.org/issue18167 opened by catlee #18168: plistlib output self-sorted dictionary http://bugs.python.org/issue18168 opened by halfjuice #18170: define built-in exceptions in Python code http://bugs.python.org/issue18170 opened by brett.cannon #18173: Add MixedTypeKey to reprlib http://bugs.python.org/issue18173 opened by ncoghlan #18174: Make regrtest with --huntrleaks check for fd leaks http://bugs.python.org/issue18174 opened by sbt #18176: Builtins documentation refers to old version of UCD. http://bugs.python.org/issue18176 opened by belopolsky #18177: Incorect quote marks in code section-headers in PDF version of http://bugs.python.org/issue18177 opened by icedream91 #18178: Redefinition of malloc(3) family of functions at build time http://bugs.python.org/issue18178 opened by cvs-src #18179: SMTP.local_hostname is undocumented http://bugs.python.org/issue18179 opened by jonash #18181: super vs. someclass.__getattribute__ http://bugs.python.org/issue18181 opened by ronaldoussoren #18182: xml.dom.createElement() does not take implicit namespaces into http://bugs.python.org/issue18182 opened by Alexander.Tobias.Heinrich #18184: Add range check for %c in PyUnicode_FromFormat http://bugs.python.org/issue18184 opened by serhiy.storchaka #18185: Error in test_set.TestVariousIteratorArgs.test_inline_methods http://bugs.python.org/issue18185 opened by syeberman #18188: ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 w http://bugs.python.org/issue18188 opened by shlomif #18189: IDLE Improvements: Unit test for Delegator.py http://bugs.python.org/issue18189 opened by JayKrish #18191: urllib2/urllib.parse.splitport does not handle IPv6 correctly http://bugs.python.org/issue18191 opened by jd #18192: Move imp.get_magic() to importlib http://bugs.python.org/issue18192 opened by brett.cannon #18193: Move imp.reload() to importlib http://bugs.python.org/issue18193 opened by brett.cannon #18194: Move imp.source_from_cache/cache_from_source to importlib http://bugs.python.org/issue18194 opened by brett.cannon #18195: error when deep copying module is confusing http://bugs.python.org/issue18195 opened by mrjbq7 #18197: insufficient error checking causes crash on windows http://bugs.python.org/issue18197 opened by maxdeliso #18199: Windows: support path longer than 260 bytes using "\\?\" prefi http://bugs.python.org/issue18199 opened by Voo #18201: distutils write into symlinks instead of replacing them http://bugs.python.org/issue18201 opened by mgorny #18202: Minor fixes for test_coding http://bugs.python.org/issue18202 opened by serhiy.storchaka #18203: Replace calls to malloc() with PyMem_Malloc() http://bugs.python.org/issue18203 opened by haypo #18206: license url in site.py should always use X.Y.Z form of version http://bugs.python.org/issue18206 opened by py.user #18207: OpenSSL may ignore seconds in notAfter http://bugs.python.org/issue18207 opened by christian.heimes #18209: Bytearray type not supported as a mutable object in the fcntl. http://bugs.python.org/issue18209 opened by vxgmichel #18211: -Werror=statement-after-declaration problem http://bugs.python.org/issue18211 opened by ronaldoussoren #18212: No way to check whether Future is finished? http://bugs.python.org/issue18212 opened by cool-RR #18213: py-bt errors on backtrace with PyRun_SimpleString and friends http://bugs.python.org/issue18213 opened by pmuldoon #18214: Stop purging modules which are garbage collected before shutdo http://bugs.python.org/issue18214 opened by sbt #18215: Script to test multiple versions of OpenSSL http://bugs.python.org/issue18215 opened by christian.heimes Most recent 15 issues with no replies (15) ========================================== #18215: Script to test multiple versions of OpenSSL http://bugs.python.org/issue18215 #18214: Stop purging modules which are garbage collected before shutdo http://bugs.python.org/issue18214 #18212: No way to check whether Future is finished? http://bugs.python.org/issue18212 #18211: -Werror=statement-after-declaration problem http://bugs.python.org/issue18211 #18209: Bytearray type not supported as a mutable object in the fcntl. http://bugs.python.org/issue18209 #18207: OpenSSL may ignore seconds in notAfter http://bugs.python.org/issue18207 #18202: Minor fixes for test_coding http://bugs.python.org/issue18202 #18189: IDLE Improvements: Unit test for Delegator.py http://bugs.python.org/issue18189 #18184: Add range check for %c in PyUnicode_FromFormat http://bugs.python.org/issue18184 #18173: Add MixedTypeKey to reprlib http://bugs.python.org/issue18173 #18166: 'value' attribute for ValueError http://bugs.python.org/issue18166 #18165: Add 'unexpected_type' to TypeError http://bugs.python.org/issue18165 #18161: call fchdir if subprocess.Popen(cwd=integer|fileobject) http://bugs.python.org/issue18161 #18144: FD leak in urllib2 http://bugs.python.org/issue18144 #18137: format(float, str): integer overflow for huge precision http://bugs.python.org/issue18137 Most recent 15 issues waiting for review (15) ============================================= #18214: Stop purging modules which are garbage collected before shutdo http://bugs.python.org/issue18214 #18202: Minor fixes for test_coding http://bugs.python.org/issue18202 #18197: insufficient error checking causes crash on windows http://bugs.python.org/issue18197 #18193: Move imp.reload() to importlib http://bugs.python.org/issue18193 #18191: urllib2/urllib.parse.splitport does not handle IPv6 correctly http://bugs.python.org/issue18191 #18189: IDLE Improvements: Unit test for Delegator.py http://bugs.python.org/issue18189 #18185: Error in test_set.TestVariousIteratorArgs.test_inline_methods http://bugs.python.org/issue18185 #18184: Add range check for %c in PyUnicode_FromFormat http://bugs.python.org/issue18184 #18181: super vs. someclass.__getattribute__ http://bugs.python.org/issue18181 #18179: SMTP.local_hostname is undocumented http://bugs.python.org/issue18179 #18176: Builtins documentation refers to old version of UCD. http://bugs.python.org/issue18176 #18174: Make regrtest with --huntrleaks check for fd leaks http://bugs.python.org/issue18174 #18167: cgi.FieldStorage fails to handle multipart/form-data when \r\n http://bugs.python.org/issue18167 #18164: Embedding Python doc incorrectly refers to LINKFORSHARED http://bugs.python.org/issue18164 #18155: csv.Sniffer.has_header doesn't escape characters used in regex http://bugs.python.org/issue18155 Top 10 most discussed issues (10) ================================= #17947: Code, test, and doc review for PEP-0435 Enum http://bugs.python.org/issue17947 16 msgs #18181: super vs. someclass.__getattribute__ http://bugs.python.org/issue18181 11 msgs #3329: API for setting the memory allocator used by Python http://bugs.python.org/issue3329 10 msgs #17860: subprocess docs lack info how to use output result http://bugs.python.org/issue17860 8 msgs #18149: filecmp.cmp() incorrect results when previously compared file http://bugs.python.org/issue18149 7 msgs #18163: Add a 'key' attribute to KeyError http://bugs.python.org/issue18163 7 msgs #10581: Review and document string format accepted in numeric data typ http://bugs.python.org/issue10581 6 msgs #14455: plistlib unable to read json and binary plist files http://bugs.python.org/issue14455 6 msgs #18188: ERROR: test_no_optimize_flag on Mageia Linux Cauldron x86-64 w http://bugs.python.org/issue18188 6 msgs #18203: Replace calls to malloc() with PyMem_Malloc() http://bugs.python.org/issue18203 6 msgs Issues closed (38) ================== #5492: Error on leaving IDLE with quit() or exit() under Linux http://bugs.python.org/issue5492 closed by roger.serwy #6632: Include more chars in the decimal codec http://bugs.python.org/issue6632 closed by belopolsky #10382: Command line error marker misplaced on unicode entry http://bugs.python.org/issue10382 closed by belopolsky #14797: Deprecate imp.find_module()/load_module() http://bugs.python.org/issue14797 closed by brett.cannon #14813: Can't build under VS2008 anymore http://bugs.python.org/issue14813 closed by christian.heimes #15239: Abandoned Tools/unicode/mkstringprep.py http://bugs.python.org/issue15239 closed by serhiy.storchaka #15767: add ModuleNotFoundError http://bugs.python.org/issue15767 closed by brett.cannon #16102: uuid._netbios_getnode() is outdated http://bugs.python.org/issue16102 closed by serhiy.storchaka #17010: Windows launcher ignores active virtual environment http://bugs.python.org/issue17010 closed by vinay.sajip #17354: TypeError when running setup.py upload --show-response http://bugs.python.org/issue17354 closed by berker.peksag #17511: Idle find function closes after each find operation http://bugs.python.org/issue17511 closed by roger.serwy #17691: Fix test discovery for test_univnewlines.py http://bugs.python.org/issue17691 closed by ezio.melotti #17838: Can't assign a different value for sys.stdin in IDLE http://bugs.python.org/issue17838 closed by roger.serwy #17903: Python launcher for windows should search path for #!/usr/bin/ http://bugs.python.org/issue17903 closed by vinay.sajip #18038: Unhelpful error message on invalid encoding specification http://bugs.python.org/issue18038 closed by serhiy.storchaka #18048: Merging test_pep263.py and test_coding.py http://bugs.python.org/issue18048 closed by serhiy.storchaka #18055: Stop using imp in IDLE http://bugs.python.org/issue18055 closed by brett.cannon #18126: Update links to NumPy resources in documentation http://bugs.python.org/issue18126 closed by ezio.melotti #18150: Duplicate test inside TestSingleDispatch http://bugs.python.org/issue18150 closed by lukasz.langa #18157: remove usage of imp.load_module() from pydoc http://bugs.python.org/issue18157 closed by brett.cannon #18160: Packaging more coherent Python http://bugs.python.org/issue18160 closed by ezio.melotti #18169: struct.pack() behaves strangely for 'L' on 64bit Linux http://bugs.python.org/issue18169 closed by skrah #18171: os.path.expanduser does not use the system encoding http://bugs.python.org/issue18171 closed by r.david.murray #18172: New easter egg: insecure string pickle http://bugs.python.org/issue18172 closed by brian.curtin #18175: os.listdir(fd) leaks fd on error http://bugs.python.org/issue18175 closed by larry #18180: Refleak in test_imp on Windows http://bugs.python.org/issue18180 closed by sbt #18183: Calling .lower() on certain unicode string raises SystemError http://bugs.python.org/issue18183 closed by benjamin.peterson #18186: 2.x subprocess contains set notation http://bugs.python.org/issue18186 closed by berker.peksag #18187: Fix broken link in Doc/library/venv.rst http://bugs.python.org/issue18187 closed by ned.deily #18190: RuntimeError raised with re.search + re.DOTALL on empty string http://bugs.python.org/issue18190 closed by serhiy.storchaka #18196: IDLE: forward apply patch for handling SystemExit http://bugs.python.org/issue18196 closed by roger.serwy #18198: unittest discover should provide a way to define discovery at http://bugs.python.org/issue18198 closed by michael.foord #18200: Update stdlib to use ModuleNotFoundError http://bugs.python.org/issue18200 closed by brett.cannon #18204: distutils error showing upload error message http://bugs.python.org/issue18204 closed by berker.peksag #18205: PyOS_ReadlineFunctionPointer violates PyMem_Malloc() API: the http://bugs.python.org/issue18205 closed by haypo #18208: Wrong bytecode generated for 'in' operation http://bugs.python.org/issue18208 closed by amaury.forgeotdarc #18210: Problem creating extension in python3.3 with mingw32 http://bugs.python.org/issue18210 closed by amaury.forgeotdarc #18158: Delete test_importhooks http://bugs.python.org/issue18158 closed by brett.cannon

1 0