Python-Dev December 2016

python-dev@python.org

63 participants
54 discussions

congrats on 3.5! Alas, windows 7 users are having problems installing it

by Laura Creighton

webmaster has already heard from 4 people who cannot install it. I sent them to the bug tracker or to python-list but they seem not to have gone either place. Is there some guide I should be sending them to, 'how to debug installation problems'? Laura

1 year, 7 months

OpenIndiana and Solaris support

by Victor Stinner

Hi, My question is simple: do we officially support Solaris and/or OpenIndiana? Jesus Cea runs an OpenIndiana buildbot slave: http://buildbot.python.org/all/buildslaves/cea-indiana-x86 "Open Indiana 32 bits" The platform module of Python says "Solaris-2.11", I don't know the exact OpenIndiana version. A lot of unit tests fail on this buildbot with MemoryError. I guess that it's related to Solaris which doesn't allow overcommit (allocating more memory than available memory on the system), or more simply because the slave has not enough memory. There is now an issue which seems specific to OpenIndiana: http://bugs.python.org/issue27847 It might impact Solaris as well, but the Solaris buildbot is offline since "684 builds". Five years ago, I reported a bug because the curses module of Python 3 doesn't build on Solaris nor OpenIndiana anymore. It seems like the bug was not fixed, and the issue is still open: http://bugs.python.org/issue13552 So my question is if we officially support Solaris and/or OpenIndiana. If yes, how can we fix issues when we only have buildbot slave which has memory errors, and no SSH access to this server? Solaris doesn't seem to be officially supported in Python, so I suggest to drop the OpenIndiana buildbot (which is failing since at least 2 years) and close all Solaris issues as "WONTFIX". Victor

4 years

Default formatting

by Serhiy Storchaka

Classes that doesn't define the __format__ method for custom PEP 3101 formatting inherits it from parents. Originally the object.__format__ method was designed as [1]: def __format__(self, format_spec): return format(str(self), format_spec) An instance is converted to string and resulting string is formatted according to format specifier. Later this design was reconsidered [2], and now object.__format__ is equivalent to: def __format__(self, format_spec): assert format_spec == '' return format(str(self), '') Non-empty format specifier is rejected. But why call format() on resulting string? Why not return resulting string as is? object.__format__ could be simpler (not just implementation, but for understanding): def __format__(self, format_spec): assert format_spec == '' return str(self) This can change the behaviour in corner case. str(self) can return not exact string, but string subclass with overloaded __format__. But I think we can ignore such subtle difference. [1] https://www.python.org/dev/peps/pep-3101/ [2] http://bugs.python.org/issue7994

4 years, 2 months

PyObject_CallFunction(func, "O", arg) special case

by Victor Stinner

Hi, The PyObject_CallFunction() function has a special case when the format string is "O", to pass exactly one Python object: * If the argument is a tuple, the tuple is unpacked: it behaves like func(*arg) * Otherwise, it behaves like func(arg) This case is not documented in the C API ! https://docs.python.org/dev/c-api/object.html#c.PyObject_CallFunction The following C functions have the special case: * PyObject_CallFunction(), _PyObject_CallFunction_SizeT() * PyObject_CallMethod(), _PyObject_CallMethod_SizeT() * _PyObject_CallMethodId(), _PyObject_CallMethodId_SizeT() I guess that it's a side effect of the implementation: the code uses Py_BuildValue() and then checks if the value is a tuple or not. Py_BuildValue() is a little bit surprising: * "i" creates an integer object * "ii" creates a tuple * "(i)" and "(ii)" create a tuple. Getting a tuple or not depends on the length of the format string. It is not obvious when you have nested tuples like "O(OO)". Because of the special case, passing a tuple as the only argument requires to write "((...))" instead of just "(...)". In the past, this special behaviour caused a bug in generator.send(arg), probably because the author of the C code implementing generator.send() wasn't aware of the special case. See the issue: http://bugs.python.org/issue21209 I found code using "O" format in the new _asyncio module, and I'm quite sure that unpacking special case is not expected. So I opened an issue: http://bugs.python.org/issue28920 Last days, I patched functions of PyObject_CallFunction() family to use internally fast calls. I implemented the special case to keep backward compatibility. I replaced a lot of code using PyObject_CallFunction() with PyObject_CallFunctionObjArgs() when the format string was only made of "O", PyObject* arguments. I made this change to optimize the code, but indirectly, it avoids also the special case for code which used exactly "O" format. See: http://bugs.python.org/issue28915 When I made these changes, I found some functions which rely the unpacking feature! * time_strptime() (change 49a7fdc0d40a) * unpickle() of _ctypes (change ceb22b8f6d32) I don't know well what we are supposed to do. I don't think that changing the behaviour of PyObject_CallFunction() to remove the special case is a good idea. It would be an obvious backward incompatible change which can break applications. I guess that the minimum is to document the special case? Victor

4 years, 2 months

Is there any remaining reason why weakref callbacks shouldn't be able to access the referenced object?

by Nathaniel Smith

Hi all, It's an old feature of the weakref API that you can define an arbitrary callback to be invoked when the referenced object dies, and that when this callback is invoked, it gets handed the weakref wrapper object -- BUT, only after it's been cleared, so that the callback can't access the originally referenced object. (I.e., this callback will never raise: def callback(ref): assert ref() is None.) AFAICT the original motivation for this seems was that if the weakref callback could get at the object, then the weakref callback would effectively be another finalizer like __del__, and finalizers and reference cycles don't mix, so weakref callbacks can't be finalizers. There's a long document from the 2.4 days about all the terrible things that could happen if arbitrary code like callbacks could get unfettered access to cyclic isolates at weakref cleanup time [1]. But that was 2.4. In the mean time, of course, PEP 442 fixed it so that finalizers and weakrefs mix just fine. In fact, weakref callbacks are now run *before* __del__ methods [2], so clearly it's now okay for arbitrary code to touch the objects during that phase of the GC -- at least in principle. So what I'm wondering is, would anything terrible happen if we started passing still-live weakrefs into weakref callbacks, and then clearing them afterwards? (i.e. making step 1 of the PEP 442 cleanup order be "run callbacks and then clear weakrefs", instead of the current "clear weakrefs and then run callbacks"). I skimmed through the PEP 442 discussion, and AFAICT the rationale for keeping the old weakref behavior was just that no-one could be bothered to mess with it [3]. [The motivation for my question is partly curiosity, and partly that in the discussion about how to handle GC for async objects, it occurred to me that it might be very nice if arbitrary classes that needed access to the event loop during cleanup could do something like def __init__(self, ...): loop = asyncio.get_event_loop() loop.gc_register(self) # automatically called by the loop when I am GC'ed; async equivalent of __del__ async def aclose(self): ... Right now something *sort* of like this is possible but it requires a much more cumbersome API, where every class would have to implement logic to fetch a cleanup callback from the loop, store it, and then call it from its __del__ method -- like how PEP 525 does it. Delaying weakref clearing would make this simpler API possible.] -n [1] https://github.com/python/cpython/blob/master/Modules/gc_weakref.txt [2] https://www.python.org/dev/peps/pep-0442/#id7 [3] https://mail.python.org/pipermail/python-dev/2013-May/126592.html -- Nathaniel J. Smith -- https://vorpus.org

4 years, 3 months

--with-fpectl changes the CPython ABI

by Nathaniel Smith

Hi all, Well, we finally got that ucs2/ucs4 stuff all sorted out (yay), but I just learned that there's another CPython build flag that also changes the ABI: --with-fpectl Specifically, it seems that if you build CPython with --with-fpectl, and then use that CPython to build an extension module, and that extension module uses PyFPE_{START,END}_PROTECT (like e.g. Cython modules do), and you then try to import that extension module on a CPython that *wasn't* built with --with-fpectl, then it will crash. This bug report has more gory details: https://github.com/numpy/numpy/issues/8415 The reverse is OK -- extensions built in a no-fpectl CPython can be imported by both no-fpectl and yes-fpectl CPythons. So one consequence is easy -- we need to make a note in the manylinux1 definition saying that you have to use a no-fpectl CPython build to make manylinux1 wheels, because that's the only way to guarantee compatibility. I just submitted a PR for this: https://github.com/python/peps/pull/166 (Fortunately the manylinux1 docker images are already set up this way, so in practice I think everyone is already doing this.) But... in general this is kind of an unfortunate issue, and it's not restricted to Linux. Should we do something? Some options: Add another ABI flag -- e.g. cp35dmf vs. cp35dm? Though AFAICT the offending macros are actually part of the allegedly stable ABI (!!), so I guess this isn't really a solution. (I'm not 100% confident about how to tell whether something is part of the stable ABI, but: Python.h unconditionally imports pyfpe.h, and pyfpe.h doesn't have any Py_LIMITED_API checks.) Drop support for fpectl entirely in 3.7 on the grounds that it's not worth the trouble? (The docs have said "don't use this" at the top forever[1], and after clicking through every hit on github code search for language = Python and string "turnon_sigfpe" [2], I found exactly 4 non-documentation usages [3], all of which are already broken in no-fpectl builds.) We obviously can't do this in a point release though, because there are lots of extant extension modules referencing these symbols. Or maybe make it so that even no-fpectl builds still export the necessary symbols so that yes-fpectl extensions don't crash on import? (This has the advantage that it can be done in a point release...) Thoughts? -n [1] https://docs.python.org/2/library/fpectl.html [2] https://github.com/search?l=Python&p=1&q=turnon_sigfpe&type=Code&utf8=%E2%9… [3] https://github.com/podhrmic/JSBSim/blob/36de9ac63c959cef5d7b2c56fb49c1a57fd… https://github.com/tmbdev/iuprlab/blob/239918b5ec0f8deecbc7c2ec1283a837d11a… https://github.com/wcs211/BEM-3D-Python/blob/874aaeffc3dac5f698f875478c3acc… https://github.com/neobonzi/SoundPlagiarism/blob/7cff7f0145217bffb3a3cebd59… -- Nathaniel J. Smith -- https://vorpus.org

4 years, 3 months

Reminder: 3.5.3 rc1 and 3.4.6 rc1 tagged tomorrow

by Larry Hastings

Just a reminder: I'll be tagging 3.5.3 rc1 and 3.4.6 rc1 tomorrow, Jan 1 2017, sometime between 24 and 36 hours from now. Please work quickly if there's anything you need to get in to either of those releases. I'm hoping that, for once, there are literally no code changes between rc1 and final. Best wishes for a happy new year, //arry/

4 years, 3 months

Document C API that is not part of the limited API

by Serhiy Storchaka

From the documentation: https://docs.python.org/3/c-api/stable.html In the C API documentation, API elements that are not part of the limited API are marked as "Not part of the limited API." But they don't. I prepared a sample patch that adds the notes to Unicode Objects and Codecs C API (http://bugs.python.org/issue29086). I'm going to add them to all C API. What are your though about formatting the note? Should it be before the description, after the description, but before the "deprecated" directive (as in the patch), or after the first paragraph of the description? Should it be on the separate line or be appended at the end of the previous paragraph, or starts the first paragraph (if before the description)? May be introduce a special directive for it?

4 years, 3 months

Summary of Python tracker Issues

by Python tracker

ACTIVITY SUMMARY (2016-12-23 - 2016-12-30) 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 5663 (+11) closed 35208 (+49) total 40871 (+60) Open issues with patches: 2449 Issues opened (32) ================== #28871: Destructor of ElementTree.Element is recursive http://bugs.python.org/issue28871 reopened by haypo #29057: Compiler failure on Mac OS X - sys/random.h http://bugs.python.org/issue29057 opened by Pam.McANulty #29058: Mark new limited C API http://bugs.python.org/issue29058 opened by serhiy.storchaka #29059: Windows: Python not using ANSI compatible console http://bugs.python.org/issue29059 opened by joseph.hackman #29062: hashlib documentation link error http://bugs.python.org/issue29062 opened by frankmillman #29063: Fixed timemodule compile warnings. http://bugs.python.org/issue29063 opened by Decorater #29067: Source archive: wrong directory attributes http://bugs.python.org/issue29067 opened by amig #29070: Integration tests for pty.spawn on Linux and all other platfor http://bugs.python.org/issue29070 opened by Cornelius Diekmann #29075: Remove Windows Vista support http://bugs.python.org/issue29075 opened by steve.dower #29076: Python 3.6 installer doesn't update "python3" shell command http://bugs.python.org/issue29076 opened by elias #29077: build failure when enabling dtrace on FreeBSD http://bugs.python.org/issue29077 opened by swills #29081: time.strptime() return wrong result http://bugs.python.org/issue29081 opened by hywl51 #29082: In 2.7.13, _ctypes.LoadLibrary no longer accepts Unicode objec http://bugs.python.org/issue29082 opened by Chi Hsuan Yen #29083: Readd PyArg_VaParse to the stable API http://bugs.python.org/issue29083 opened by serhiy.storchaka #29084: C API of OrderedDict http://bugs.python.org/issue29084 opened by serhiy.storchaka #29086: Document C API that is not part of the limited API http://bugs.python.org/issue29086 opened by serhiy.storchaka #29090: python34.dll crash http://bugs.python.org/issue29090 opened by MikeH #29092: Sync os.stat's doc and doc string http://bugs.python.org/issue29092 opened by xiang.zhang #29093: Windows launcher breaks history in Git Bash http://bugs.python.org/issue29093 opened by evan_ #29094: Regression in zipfile writing in 2.7.13 http://bugs.python.org/issue29094 opened by Peter Ebden #29096: Signal Handlers reliably cause UnboundLocalErrors http://bugs.python.org/issue29096 opened by Ted Meyer #29097: datetime.fromtimestamp(t) when 0 <= t <= 86399 fails on Python http://bugs.python.org/issue29097 opened by pekka.klarck #29098: document minimum sqlite version http://bugs.python.org/issue29098 opened by carlwgeorge #29099: sqlite3 timestamp converter cannot handle timezone http://bugs.python.org/issue29099 opened by bozo.kopic #29100: Core dump / OverflowError for datetime.fromtimestamp with over http://bugs.python.org/issue29100 opened by Jordon Phillips #29102: Add an id field to PyInterpreterState. http://bugs.python.org/issue29102 opened by eric.snow #29104: Left bracket remains in format string result when '\' preceeds http://bugs.python.org/issue29104 opened by Jim Fasarakis-Hilliard #29105: code or doc improvement for logging.handlers.RotatingFileHandl http://bugs.python.org/issue29105 opened by redstone-cold #29107: traceback module incorrectly formats args-less syntax errors http://bugs.python.org/issue29107 opened by Naftali.Harris #29108: Python 3.6.0 multiprocessing map_async callback http://bugs.python.org/issue29108 opened by Jose Miguel Colella #29110: [patch] Fix file object leak in `aifc.open` when given invalid http://bugs.python.org/issue29110 opened by azhang #29113: modulefinder no longer finds all required modules for Python i http://bugs.python.org/issue29113 opened by adamwill Most recent 15 issues with no replies (15) ========================================== #29113: modulefinder no longer finds all required modules for Python i http://bugs.python.org/issue29113 #29110: [patch] Fix file object leak in `aifc.open` when given invalid http://bugs.python.org/issue29110 #29107: traceback module incorrectly formats args-less syntax errors http://bugs.python.org/issue29107 #29105: code or doc improvement for logging.handlers.RotatingFileHandl http://bugs.python.org/issue29105 #29100: Core dump / OverflowError for datetime.fromtimestamp with over http://bugs.python.org/issue29100 #29098: document minimum sqlite version http://bugs.python.org/issue29098 #29094: Regression in zipfile writing in 2.7.13 http://bugs.python.org/issue29094 #29092: Sync os.stat's doc and doc string http://bugs.python.org/issue29092 #29086: Document C API that is not part of the limited API http://bugs.python.org/issue29086 #29083: Readd PyArg_VaParse to the stable API http://bugs.python.org/issue29083 #29081: time.strptime() return wrong result http://bugs.python.org/issue29081 #29075: Remove Windows Vista support http://bugs.python.org/issue29075 #29070: Integration tests for pty.spawn on Linux and all other platfor http://bugs.python.org/issue29070 #29067: Source archive: wrong directory attributes http://bugs.python.org/issue29067 #29063: Fixed timemodule compile warnings. http://bugs.python.org/issue29063 Most recent 15 issues waiting for review (15) ============================================= #29110: [patch] Fix file object leak in `aifc.open` when given invalid http://bugs.python.org/issue29110 #29104: Left bracket remains in format string result when '\' preceeds http://bugs.python.org/issue29104 #29102: Add an id field to PyInterpreterState. http://bugs.python.org/issue29102 #29099: sqlite3 timestamp converter cannot handle timezone http://bugs.python.org/issue29099 #29097: datetime.fromtimestamp(t) when 0 <= t <= 86399 fails on Python http://bugs.python.org/issue29097 #29092: Sync os.stat's doc and doc string http://bugs.python.org/issue29092 #29086: Document C API that is not part of the limited API http://bugs.python.org/issue29086 #29082: In 2.7.13, _ctypes.LoadLibrary no longer accepts Unicode objec http://bugs.python.org/issue29082 #29070: Integration tests for pty.spawn on Linux and all other platfor http://bugs.python.org/issue29070 #29063: Fixed timemodule compile warnings. http://bugs.python.org/issue29063 #29062: hashlib documentation link error http://bugs.python.org/issue29062 #29059: Windows: Python not using ANSI compatible console http://bugs.python.org/issue29059 #29058: Mark new limited C API http://bugs.python.org/issue29058 #29057: Compiler failure on Mac OS X - sys/random.h http://bugs.python.org/issue29057 #29054: pty.py: pty.spawn hangs after client disconnect over nc (netca http://bugs.python.org/issue29054 Top 10 most discussed issues (10) ================================= #23903: Generate PC/python3.def by scraping headers http://bugs.python.org/issue23903 15 msgs #29048: Coverage influence tests, make some of them fail http://bugs.python.org/issue29048 14 msgs #29062: hashlib documentation link error http://bugs.python.org/issue29062 13 msgs #29102: Add an id field to PyInterpreterState. http://bugs.python.org/issue29102 13 msgs #29058: Mark new limited C API http://bugs.python.org/issue29058 10 msgs #29057: Compiler failure on Mac OS X - sys/random.h http://bugs.python.org/issue29057 9 msgs #29104: Left bracket remains in format string result when '\' preceeds http://bugs.python.org/issue29104 9 msgs #29097: datetime.fromtimestamp(t) when 0 <= t <= 86399 fails on Python http://bugs.python.org/issue29097 8 msgs #29099: sqlite3 timestamp converter cannot handle timezone http://bugs.python.org/issue29099 8 msgs #26382: List object memory allocator http://bugs.python.org/issue26382 7 msgs Issues closed (49) ================== #9770: curses.ascii.isblank() function is broken. It confuses backspa http://bugs.python.org/issue9770 closed by serhiy.storchaka #13051: Infinite recursion in curses.textpad.Textbox http://bugs.python.org/issue13051 closed by serhiy.storchaka #14483: inspect.getsource fails to read a file of only comments http://bugs.python.org/issue14483 closed by r.david.murray #25778: winreg.EnumValue does not truncate strings correctly http://bugs.python.org/issue25778 closed by steve.dower #26758: Unnecessary format string handling for no argument slot wrappe http://bugs.python.org/issue26758 closed by inada.naoki #28427: WeakValueDictionary next bug (with multithreading) http://bugs.python.org/issue28427 closed by pitrou #28446: pyvenv generates malformed hashbangs for scripts http://bugs.python.org/issue28446 closed by vinay.sajip #28675: about PEP 528 / PEP 529 http://bugs.python.org/issue28675 closed by steve.dower #28902: 3.6.0rc1 installer fails to install / uninstall. http://bugs.python.org/issue28902 closed by steve.dower #28954: Incorrect EBNF rule of keywords_arguments http://bugs.python.org/issue28954 closed by martin.panter #28960: Small typo in Thread.join docs http://bugs.python.org/issue28960 closed by martin.panter #28998: Unifying Long Integers and Integers in 2.7 http://bugs.python.org/issue28998 closed by serhiy.storchaka #29003: sqlite3: can't run VACUUM on Python 3.6 http://bugs.python.org/issue29003 closed by berker.peksag #29004: binascii.crc_hqx() implements CRC-CCITT http://bugs.python.org/issue29004 closed by martin.panter #29025: random.seed() relation to hash() function and its determinism http://bugs.python.org/issue29025 closed by rhettinger #29037: Python 2.7.13 prints version header and exits immediately on W http://bugs.python.org/issue29037 closed by steve.dower #29047: Where are the test results stored? http://bugs.python.org/issue29047 closed by patriki #29049: Lazy GC tracking frame http://bugs.python.org/issue29049 closed by inada.naoki #29055: random.choice on empty sequence should hide previous exception http://bugs.python.org/issue29055 closed by rhettinger #29056: logging.Formatter doesn't respect more than one formatExceptio http://bugs.python.org/issue29056 closed by vinay.sajip #29060: Changing the installation location still adds AppData filepath http://bugs.python.org/issue29060 closed by steve.dower #29061: secrets.randbelow(-1) hangs http://bugs.python.org/issue29061 closed by rhettinger #29064: Package numpy can't be used normally http://bugs.python.org/issue29064 closed by xiang.zhang #29065: SSL module problem on Python 3.6.0 and macOS Sierra http://bugs.python.org/issue29065 closed by ned.deily #29066: PIP doesn't honor --trusted-host or --cert options http://bugs.python.org/issue29066 closed by ned.deily #29068: Fix example code for PyErr_Fetch http://bugs.python.org/issue29068 closed by serhiy.storchaka #29069: Default PyPI URL in docs is not what is really in code http://bugs.python.org/issue29069 closed by berker.peksag #29071: IDLE doesn't highlight f-strings properly http://bugs.python.org/issue29071 closed by terry.reedy #29072: the message of help(os.environ.setdefault) have some error http://bugs.python.org/issue29072 closed by r.david.murray #29073: bytearray.__mod__() truncates on first \x00 http://bugs.python.org/issue29073 closed by serhiy.storchaka #29074: repr doesn't give full result for this re math result http://bugs.python.org/issue29074 closed by mrabarnett #29078: Example in Section 8.1.5 time Objects is broken http://bugs.python.org/issue29078 closed by xiang.zhang #29079: pathlib.resolve() causes infinite loop on Windows http://bugs.python.org/issue29079 closed by steve.dower #29080: unnecessary hg required for build version 3.6 on Windows http://bugs.python.org/issue29080 closed by steve.dower #29085: Python 3.6 on Windows doesn't seed Random() well enough http://bugs.python.org/issue29085 closed by python-dev #29087: UCS4 support functions are not implemented http://bugs.python.org/issue29087 closed by serhiy.storchaka #29088: Inconsistent use of underscore in names that start with "is" http://bugs.python.org/issue29088 closed by r.david.murray #29089: dictionary keys described incorrectly in tutorial http://bugs.python.org/issue29089 closed by rhettinger #29091: Python 3.5+ socket.socketpair fallback incorrectly implemented http://bugs.python.org/issue29091 closed by benjamin.peterson #29095: Compiling Python 3.6 from source on MacOS X Sierra http://bugs.python.org/issue29095 closed by ned.deily #29101: Nested lambdas in setattr() lose context in Python 2.7 http://bugs.python.org/issue29101 closed by benjamin.peterson #29103: Make enum.py pep8 compliant http://bugs.python.org/issue29103 closed by rhettinger #29106: get-pip.py fails with Python 3.6 embed Windows http://bugs.python.org/issue29106 closed by ammar2 #29109: Small doc improvements for tracemalloc http://bugs.python.org/issue29109 closed by haypo #29111: Strange signature for memoryview constructor http://bugs.python.org/issue29111 closed by skrah #29112: questionable wording in sequences documentation http://bugs.python.org/issue29112 closed by xiang.zhang #29114: __class__ not exists in the method which bounded by types.Meth http://bugs.python.org/issue29114 closed by ncoghlan #29115: distutils.core.setup does not let people set 'bugtrack_url'. http://bugs.python.org/issue29115 closed by berker.peksag #1446619: extended slice behavior inconsistent with docs http://bugs.python.org/issue1446619 closed by martin.panter

4 years, 3 months

Just added AnyChart JS Charts integration templates for easier dataviz with Python and MySQL

by Andrey Khachaturov

We at AnyChart JS Charts <http://www.anychart.com> have just released a series of 20+ integration templates to help web developers add interactive charts, maps, stock and financial graphs, Gantt charts, and dashboards to web apps much easier, no matter what your technology stack is. In particular, now there are two templates for Python in our Technical Integration <http://www.anychart.com/integrations/> collection, all distributed under the Apache 2.0 license and forkable on GitHub: - *Python*, *Flask* and *MySQL* (GitHub <https://github.com/anychart-integrations/python-flask-mysql-template>); - *Python*, *Django* and *MySQL* (GitHub <https://github.com/anychart-integrations/python-django-mysql-template>). Check that out, and ask your questions if any. Thanks.

4 years, 3 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

Python-Dev December 2016