Re: [Python-Dev] django_v2 benchmark compatibility fix for Python 3.6
Hi all, Based on the feedback I received, I updated the patch to introduce django_v3 benchmark, which uses django 1.8. Also, django_v2 was deprecated for Python 3.6 and above. In order for django_v3 to work, the latest django release must be present in lib/Django-1.8. Django-1.8 is attached as a zip file because the patch would be too large if it included all these files. In order for the modifications to work, extract the archive to lib/Django-1.8 . Please see the issue here: http://bugs.python.org/issue24934 Thank you, Florin Papa On Tue, 25 Aug 2015 at 08:31 R. David Murray wrote: On Tue, 25 Aug 2015 11:18:54 -0400, Terry Reedy wrote: > On 8/25/2015 10:51 AM, R. David Murray wrote: > > On Tue, 25 Aug 2015 13:11:37 -, "Papa, Florin" > > wrote: > >> My name is Florin Papa and I work in the Server Languages Optimizations > >> Team at Intel Corporation. > >> > >> I would like to submit a patch that solves compatibility issues of the > >> django_v2 benchmark in the Grand Unified Python Benchmark. The django_v2 > >> benchmark uses inspect.getargspec(), which is deprecated and was removed > >> in Python 3.6. Therefore, it crashes with the message "ImportError: cannot > >> import name 'getargspec'" when using the latest version of Python on the > >> default branch. > >> > >> The patch modifies the benchmark to use inspect.signature() when Python > >> version is 3.6 or above and keep using inspect.getargspec() otherwise. > > > > Note that Papa has submitted the patch to the tracker: > > > > http://bugs.python.org/issue24934 > > > > I'm not myself sure how we are maintaining that repo > > (https://hg.python.org/benchmarks), but it does seem like the bug > > tracker is the right place for such a patch. > > Is the django_v2 benchmark original to benchmarks, or a copy from django? Yeah, that's one question that was in my mind when I said I don't know how we maintain that repo. I'm pretty sure it was originally a copy of the django project, but how do we maintain it? It's maintained by primarily Antoine and me occasionally doing stuff to it. =) Traditionally bugs have been reported to bugs.python.org. As for the django_v2 benchmark, it was created by Unladen Swallow (it's v2 because it was updated to work with Django 1.5 so as to get Python 3 support for the benchmark). IOW it's out own benchmark and we can do whatever we want with it. ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Building Extensions for Python 3.5 on Windows
On 25Aug2015 2153, Terry Reedy wrote:
On 8/25/2015 2:17 PM, Steve Dower wrote:
I've written up a long technical blog post about the compiler and CRT
changes in Python 3.5, which will be of interest to those who build and
distribute native extensions for Windows.
http://stevedower.id.au/blog/building-for-python-3-5/
Hopefully it puts some of the changes we've made into a context where
they don't just look like unnecessary pain. Feedback and discussion
welcome, either on these lists or on the post itself.
This is an excellent technical writeup. Can it be linked to from the
devguide, or maybe the C-API docs, if they do not contain everything in
the post?
I probably need to go through the "Building C and C++ Extensions on
Windows" chapter (https://docs.python.org/3.5/extending/windows.html)
and update it. Judging by the note near the top ("For example, if you
are using Python 2.2.1") it's a little out of date :)
Things I'd like to see on that page:
* setup.py example to build simple extensions
* command-line commands to build directly
* VS walkthrough for setting up a project (like what is there now)
* MinGW walkthrough for building extensions via distutils or directly
(I'll need some help with this one)
* deeper discussion on DLLs/static linking/distribution (like section
4.3 now, plus details from my post)
On the VS walkthrough, my team at work already has a strong interest
(and vague plans) to publish VS templates for building Python
extensions, which naturally come with docs and maybe a video walkthrough
(like https://youtu.be/D9RlT06a1EI, which I did for Python 3.4 without a
template).
If there's no opposition, it may be neater to link to that rather than
walking through VS in Python's docs - then this section would just cover
the command line invocations. I have no issues with linking to other
IDE's templates/walkthroughs, but I don't know of any that exist yet.
Cheers,
Steve
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
[Python-Dev] Testing tkinter on Linux
None of the linux buildbots run with X enabled. Consequently none of the tkinter (or tkinter user) gui tests are run on Linux. It was thus pointed out to me, during discussion of using ttk widgets in Idle, that we do not really know if ttk works on the variety of Linux systems (beyond the one Serhiy uses) and that I should look into this. I asked on python-list for help, by linux users running python3 -m test -ugui test_tk test_ttk_guionly test_idle Seven people did so with Debian Jessie, Debian Wheezy, Gentoo, Mint, openSUSE, and Ubuntu (x2). One machine failed once with the ttk test, and then passed. Another failed the tk test until a mis-configuration was fixed. So tkinter, and ttk in particular, seems to be working on linux. Do any of the core devs who run the test suite on Linux do so with -uall or -ugui? The gui tests above take about 10 seconds (mostly the tk test) on my machine, with some flashing boxes near the end. -- Terry Jan Reedy ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Re: [Python-Dev] Testing tkinter on Linux
On Thu, Aug 27, 2015 at 2:20 PM, Terry Reedy wrote: > None of the linux buildbots run with X enabled. Consequently none of the > tkinter (or tkinter user) gui tests are run on Linux. It was thus pointed > out to me, during discussion of using ttk widgets in Idle, that we do not > really know if ttk works on the variety of Linux systems (beyond the one > Serhiy uses) and that I should look into this. If it helps, my buildbot has full GUI services, so if there's a simple way to tell it to run the GUI tests every time, they should pass. ChrisA ___ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
