Re: [Python-Dev] 2.6 branch in Mercurial?
Cool, thanks to Ned and Zach. Hg never gets allocated very many neurons in my brain. Then there's the whole brain-in-neutral aspect of things which makes me fail to consider there might be help and/or closed branches which aren't displayed... Sorry for the distraction. Skip ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Implementing (parts of) copy module in C
First, apologies if this isn't the appropriate list; I trust I'll be nudged in the right direction. I'm using (and contributing to) an application which spends a significant part of its startup time calling copy.deepcopy, so I thought I'd try to write a C extension to speed this up. Aside from avoiding the interpreter overhead, we should also save some time by having access to pre-sizing the containers. My plan is to let the C code handle the [at least in my case] most common stuff - atomic types, dicts, lists, tuples etc., while falling back to the python implementation for the stuff that's inconvenient to do in C, or which just hasn't been done yet - this allows a simple piecemeal approach. Since my main use case runs on 2.7 only, I've started from the 2.7 branch, and have some working code (passes the test suite, speedup between 3x-30x depending on the data structure). Before spending time forward-porting this to Python 3, I'd like to hear if there's any interest in it? I would of course also be very interested in getting it into 2.7.x, but I assume that's impossible(?). Where/how should RFC patches be posted? Thanks, Rasmus ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Benchmarking Python and micro-optimizations
Hi, Thanks first for that, it's very interesting. About to enrich benchmark suite, I might have a suggestion: We might add REST/JSON scenarios, because a lot of people use Python for that. It isn't certainly not the best REST/JSON scenarios, because they have a small payload, but better than nothing: https://www.techempower.com/benchmarks/#section=code&hw=peak&test=fortune Moreover, we already have several implementations for the most populars Web frameworks: https://github.com/TechEmpower/FrameworkBenchmarks/tree/master/frameworks/Python The drawback is that a lot of tests need a database. I can help if you're interested in. Have a nice week. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Implementing (parts of) copy module in C
Rasmus Villemoes writes: > First, apologies if this isn't the appropriate list; I trust I'll be > nudged in the right direction. Given the relatively advanced state of patch, I doubt that this is the *wrong* list. However, you would probably benefit from posting to python-l...@python.org to collect use cases. (We don't "vote" on such additions. Rather the senior devs consider whether the use cases seem general enough to justify on-going maintenance costs for new code.) > I would of course also be very interested in getting it into 2.7.x, > but I assume that's impossible(?). That is correct. This is clearly a feature, and 2.7 currently is accepting only security-related patches (broadly construed -- a sufficiently severe bug, such as a crash or infloop, is security- related because it could be used to implement a DoS attack). > Where/how should RFC patches be posted? To the issue tracker, bugs.python.org. A follow-up here (and if you choose to post to python-list, there) to mention the issue number and URL is a good idea. ___ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
