From charlesr.harris at gmail.com Sun Jan 1 19:04:08 2017 From: charlesr.harris at gmail.com (Charles R Harris) Date: Sun, 1 Jan 2017 17:04:08 -0700 Subject: NumPy 1.12.0rc2 release. Message-ID: Hi All, I'm pleased to announce the NumPy 1.12.0rc2 New Year's release. This release supports Python 2.7 and 3.4-3.6. Wheels for all supported Python versions may be downloaded from PiPY , the tarball and zip files may be downloaded from Github . The release notes and files hashes may also be found at Github . NumPy 1.12.0rc 2 is the result of 413 pull requests submitted by 139 contributors and comprises a large number of fixes and improvements. Among the many improvements it is difficult to pick out just a few as standing above the others, but the following may be of particular interest or indicate areas likely to have future consequences. * Order of operations in ``np.einsum`` can now be optimized for large speed improvements. * New ``signature`` argument to ``np.vectorize`` for vectorizing with core dimensions. * The ``keepdims`` argument was added to many functions. * New context manager for testing warnings * Support for BLIS in numpy.distutils * Much improved support for PyPy (not yet finished) Enjoy, Chuck From larry at hastings.org Mon Jan 2 21:20:56 2017 From: larry at hastings.org (Larry Hastings) Date: Mon, 2 Jan 2017 18:20:56 -0800 Subject: [RELEASED] Python 3.4.6rc1 and Python 3.5.3rc1 are now available Message-ID: <4437910e-0f87-2d2d-062e-8e4fc0be2a58@hastings.org> On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm pleased to announce the availability of Python 3.4.6rc1 and Python 3.5.6rc1. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. Python 3.4 now only receives security fixes, not bug fixes, and Python 3.4 releases are source code only--no more official binary installers will be produced. Python 3.5 is still in active "bug fix" mode. Python 3.5.3rc1 contains many incremental improvements over Python 3.5.2. Both these releases are "release candidates". They should not be considered the final releases, although the final releases should contain only minor differences. Python users are encouraged to test with these releases and report any problems they encounter. You can find Python 3.4.6rc1 here: https://www.python.org/downloads/release/python-346rc1/ And you can find Python 3.5.3rc1 here: https://www.python.org/downloads/release/python-353rc1/ Python 3.4.6 final and Python 3.5.3 final are both scheduled for release on January 16th, 2017. Happy New Year, //arry/ From tds333 at mailbox.org Wed Jan 4 06:03:50 2017 From: tds333 at mailbox.org (Wolfgang) Date: Wed, 4 Jan 2017 12:03:50 +0100 Subject: StdConfigParser 1.0 release Message-ID: <4f6f84ee-4688-eedf-eedd-e2e062133b70@mailbox.org> Announcing the release of StdConfigParser 1.0 What is it? ----------- This is the Python configparser with an extra class StdConfigParser. The StdConfigParser class uses specified parameters to initialize the Python ConfigParser and adds some useful converters. The result is a simple well defined syntax for the INI file. See it as a preconfigured ConfigParser class for you. It allows interoperability in configuration between different projects. Also contains everything to be a full backport of the configparser module from Python 3.5 to Python 2.7, 3.3, 3.4. Everything in one module easy to vendor or install no extra dependencies. Note ---- Even if you don't need the additional class StdConfigParser this module is useful as a backport of the ConfigParser class with the features from Python 3.5 to older Python versions. All in one file without the namespace or ".pth" problems of other backports. Also easy to vendor! What's new in 1.0 ----------------- - Support Python 3.6 - Improve stability in error cases. Test improved error reporting. Links ----- - Download: https://pypi.python.org/pypi/StdConfigParser - Source: https://github.com/tds333/stdconfigparser - Documentation: http://stdconfigparser.readthedocs.io/en/latest/index.html Kind regards, Wolfgang From jendrikseipp at web.de Thu Jan 5 06:22:31 2017 From: jendrikseipp at web.de (Jendrik Seipp) Date: Thu, 5 Jan 2017 12:22:31 +0100 Subject: Vulture 0.12 Message-ID: <1184553c-c3f6-7cc2-57f2-bf3d5e1308d8@web.de> vulture - Find dead code ======================== Vulture finds unused classes, functions and variables in your code. This helps you cleanup and find errors in your programs. If you run it on both your library and test suite you can find untested code. Due to Python's dynamic nature, static code analyzers like vulture are likely to miss some dead code. Also, code that is only called implicitly may be reported as unused. Nonetheless, vulture can be a helpful tool for higher code quality. Download ======== http://pypi.python.org/pypi/vulture Features ======== * fast: uses static code analysis * lightweight: only one module * tested: tests itself and has 100% test coverage * complements pyflakes and has the same output syntax * supports Python 2.6, 2.7 and 3.x News ==== * Detect unused imports. * Use tokenize.open() on Python >= 3.2 for reading input files, assume UTF-8 encoding on older Python versions. Cheers, Jendrik From anthony.tuininga at gmail.com Sat Jan 7 18:50:32 2017 From: anthony.tuininga at gmail.com (Anthony Tuininga) Date: Sat, 7 Jan 2017 16:50:32 -0700 Subject: cx_Freeze 5.0.1 Message-ID: What is cx_Freeze? cx_Freeze is a set of scripts and modules for freezing Python scripts into executables, in much the same way that py2exe and py2app do. Unlike these two tools, cx_Freeze is cross platform and should work on any platform that Python itself works on. It supports Python 2.7 or higher, including Python 3. Where do I get it? http://cx-freeze.sourceforge.net What's new? http://cx_freeze.readthedocs.org/en/latest/releasenotes.html From mal at python.org Fri Jan 6 11:00:57 2017 From: mal at python.org (M.-A. Lemburg) Date: Fri, 6 Jan 2017 17:00:57 +0100 Subject: ANN: Python Events Calendar - Please submit your 2017 events Message-ID: <3437cbdf-ddbc-db86-746c-772dd616a09c@python.org> [Please help spread the word by forwarding to other relevant mailing lists, user groups, etc. world-wide; thanks :-)] ________________________________________________________________________ ANNOUNCING Python Events Calendars - Please submit your 2017 events maintained by the Python Software Foundation (PSF) and a group of volunteers ________________________________________________________________________ INTRODUCTION As some of you may know, the PSF has a team of volunteers who are maintaining a set of central Python event calendars. We currently have two calendars in place: * Python Events Calendar - meant for conferences and larger gatherings focusing on Python or a related technology (in whole or in part) * Python User Group Calendar - meant for user group events and other smaller local events The calendars are displayed on https://www.python.org/events/ and http://pycon.org/. There's also a map mashup to show events near you or get an overview of what currently going in the Python community: http://lmorillas.github.io/python_events/ You can subscribe to the calendars using iCal and RSS feeds and also embed the calendar widgets on your sites. We have also added a Twitter feed @PythonEvents to get immediate updates whenever a new event is added. Please see our wiki page for details: https://wiki.python.org/moin/PythonEventsCalendar The calendars are open to the world-wide Python community, so you can have local user group events, as well as regional and international conference events added to the calendars. ________________________________________________________________________ NEWS Looking back, the calendars have proven to be a great tool for the Python community to connect, with more than 250 conferences and more than a hundred of user group events listed since 2012. We would therefore like to encourage everyone to submit their 2017 events, so that the Python community can get a better overview over what's happening in Python land. ________________________________________________________________________ ADDING EVENTS Please see the instructions at https://wiki.python.org/moin/PythonEventsCalendar#Submitting_an_Event for details on how to submit an event. We've made it really easy for you: just need to send an email to our team address using the email template we provide for this. Thanks. ________________________________________________________________________ MORE INFORMATION More information on the calendars, the URLs, feed links, IDs, embedding, etc. is available on the wiki: https://wiki.python.org/moin/PythonEventsCalendar Enjoy, -- Marc-Andre Lemburg Python Software Foundation http://www.python.org/psf/ http://www.malemburg.com/ From mmanns at gmx.net Sun Jan 8 08:08:07 2017 From: mmanns at gmx.net (Martin Manns) Date: Sun, 8 Jan 2017 14:08:07 +0100 Subject: [ANN] pyspread 1.1 Message-ID: <20170108140807.6856a91d@Fuddel.mynet> ============== pyspread 1.1 ============== Pyspread 1.1 has been released. About pyspread ============== Pyspread is a non-traditional spreadsheet application that is based on and written in the programming language Python. The goal of pyspread is to be the most pythonic spreadsheet application. Pyspread is free software. It is released under the GPL v3. Project website: https://manns.github.io/pyspread/ Download page: https://pypi.python.org/pypi/pyspread Source code: https://github.com/manns/pyspread Release 1.1 focuses on usability ================================ Besides feedback from visualization of statistics analyzes, feedback from using pyspread as a presentation tool has been taken into account. Pre-releases of 1.1 have been successfully used for presentations with up to 50 pages that include multiple videos. New features ============ * Video support (requires libvlc). * Spell checking (requires pyenchant). * Copy and paste of cell formats (only) via ++C and ++V . Copying formats has been decoupled from content in order to avoid unwanted side effects that can be experienced in current Office suites. * fits the grid to the screen size if the grid is not too large. * OpenDocument Spreadsheet (ods) file open support (requires pyodf, only cell values, yet). * Alpha blending option added to multiple chart types. Usability improvements ====================== * New panel for table choice for better usability with poor mouse wheels. * The default UI language has been changed from system default to English. * The current row and column now is highlighted in the grid labels. * In fullscreen mode, arrow keys and space navigate through the tables. * The cell cursor is now hidden in fullscreen mode. * Changing preferences now refreshes the grid. * The cell editor is now closed and all changes are discarded when the table is switched. * The UI language can now be chosen from preferences dialog. * The default open and save filetypes can now be set in preferences dialog, which simplifies using pysu files via git. Major bug fixes =============== * Unmerging cells no longer leads to strange side effects. * Cell attribute access is now faster if many tables are present. * The cell editor is now closed and all changes are discarded when the table is switched. * Xls file import made independent from screen resolution. * The current directory is now changed to the directory, so that relative file access is possible. * Concurrent saving operations fixed. Known issues ============ * Button cells and video cells may require two clicks instead of one. * Fonts in presentations may differ between platforms, which can cause undesirable differences line breaks. * ODS import is still very limited and does not cover cell formatting. Enjoy Martin -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 228 bytes Desc: OpenPGP digital signature URL: From news at news.bbs.geek.nz Sun Jan 1 00:04:08 2017 From: news at news.bbs.geek.nz (news at news.bbs.geek.nz) Date: Sun, 01 Jan 2017 17:04:08 +1200 Subject: NumPy 1.12.0rc2 release. Message-ID: <866891649@f38.n261.z1.binkp.net> Hi All, I'm pleased to announce the NumPy 1.12.0rc2 New Year's release. This release supports Python 2.7 and 3.4-3.6. Wheels for all supported Python versions may be downloaded from PiPY , the tarball and zip files may be downloaded from Github . The release notes and files hashes may also be found at Github . NumPy 1.12.0rc 2 is the result of 413 pull requests submitted by 139 contributors and comprises a large number of fixes and improvements. Among the many improvements it is difficult to pick out just a few as standing above the others, but the following may be of particular interest or indicate areas likely to have future consequences. * Order of operations in ``np.einsum`` can now be optimized for large speed improvements. * New ``signature`` argument to ``np.vectorize`` for vectorizing with core dimensions. * The ``keepdims`` argument was added to many functions. * New context manager for testing warnings * Support for BLIS in numpy.distutils * Much improved support for PyPy (not yet finished) Enjoy, Chuck From news at news.bbs.geek.nz Wed Jan 4 19:22:30 2017 From: news at news.bbs.geek.nz (news at news.bbs.geek.nz) Date: Thu, 05 Jan 2017 12:22:30 +1200 Subject: Vulture 0.12 Message-ID: <3728908121@f38.n261.z1.binkp.net> vulture - Find dead code ======================== Vulture finds unused classes, functions and variables in your code. This helps you cleanup and find errors in your programs. If you run it on both your library and test suite you can find untested code. Due to Python's dynamic nature, static code analyzers like vulture are likely to miss some dead code. Also, code that is only called implicitly may be reported as unused. Nonetheless, vulture can be a helpful tool for higher code quality. Download ======== http://pypi.python.org/pypi/vulture Features ======== * fast: uses static code analysis * lightweight: only one module * tested: tests itself and has 100% test coverage * complements pyflakes and has the same output syntax * supports Python 2.6, 2.7 and 3.x News ==== * Detect unused imports. * Use tokenize.open() on Python >= 3.2 for reading input files, assume UTF-8 encoding on older Python versions. Cheers, Jendrik From news at news.bbs.geek.nz Tue Jan 3 19:03:50 2017 From: news at news.bbs.geek.nz (news at news.bbs.geek.nz) Date: Wed, 04 Jan 2017 12:03:50 +1200 Subject: StdConfigParser 1.0 release Message-ID: <3916218146@f38.n261.z1.binkp.net> Announcing the release of StdConfigParser 1.0 What is it? ----------- This is the Python configparser with an extra class StdConfigParser. The StdConfigParser class uses specified parameters to initialize the Python ConfigParser and adds some useful converters. The result is a simple well defined syntax for the INI file. See it as a preconfigured ConfigParser class for you. It allows interoperability in configuration between different projects. Also contains everything to be a full backport of the configparser module from Python 3.5 to Python 2.7, 3.3, 3.4. Everything in one module easy to vendor or install no extra dependencies. Note ---- Even if you don't need the additional class StdConfigParser this module is useful as a backport of the ConfigParser class with the features from Python 3.5 to older Python versions. All in one file without the namespace or ".pth" problems of other backports. Also easy to vendor! What's new in 1.0 ----------------- - Support Python 3.6 - Improve stability in error cases. Test improved error reporting. Links ----- - Download: https://pypi.python.org/pypi/StdConfigParser - Source: https://github.com/tds333/stdconfigparser - Documentation: http://stdconfigparser.readthedocs.io/en/latest/index.html Kind regards, Wolfgang From news at news.bbs.geek.nz Mon Jan 2 01:20:56 2017 From: news at news.bbs.geek.nz (news at news.bbs.geek.nz) Date: Mon, 02 Jan 2017 18:20:56 +1200 Subject: [RELEASED] Python 3.4.6rc1 and Python 3.5.3rc1 are now available Message-ID: <2132643565@f38.n261.z1.binkp.net> On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm pleased to announce the availability of Python 3.4.6rc1 and Python 3.5.6rc1. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. Python 3.4 now only receives security fixes, not bug fixes, and Python 3.4 releases are source code only--no more official binary installers will be produced. Python 3.5 is still in active "bug fix" mode. Python 3.5.3rc1 contains many incremental improvements over Python 3.5.2. Both these releases are "release candidates". They should not be considered the final releases, although the final releases should contain only minor differences. Python users are encouraged to test with these releases and report any problems they encounter. You can find Python 3.4.6rc1 here: https://www.python.org/downloads/release/python-346rc1/ And you can find Python 3.5.3rc1 here: https://www.python.org/downloads/release/python-353rc1/ Python 3.4.6 final and Python 3.5.3 final are both scheduled for release on January 16th, 2017. Happy New Year, //arry/ From serge.guelton at telecom-bretagne.eu Fri Jan 6 13:20:11 2017 From: serge.guelton at telecom-bretagne.eu (serge guelton) Date: Fri, 6 Jan 2017 19:20:11 +0100 Subject: [ANN] Pythran O.8.0 is out Message-ID: <20170106182011.q6p6dmhutjc6ov6c@lakota> (sorry for the double posting, if any) Dear pythraners and pythonists, The Pythran team (a great deal of 2 active developers) is delighted to announce the release of Pythran 0.8.0, available on the traditional channels: - pypi: https://pypi.python.org/pypi/pythran - github: https://github.com/serge-sans-paille/pythran What is it? =========== Pythran is a static compiler for numerical kernels written in Python + Numpy. It basically turns Python-compatible modules into native ones, eventually vectorized and parallelized. More Infos ========== We periodically publish some technical details about Pythran internal on the blog: http://serge-sans-paille.github.io/pythran-stories/ It is open to third-party contribution! Changelog ========= * Python 3 support * (unsound) Type Checker * Various bug fixes and perf improvement, as usual Acknowledgments =============== Kudos to Pierrick Brunet and to all the bug reporters and patch providers that helped a lot for this release! Special thanks to lesshaste for his critical bugreport! From tmoldere at vub.ac.be Fri Jan 6 10:16:23 2017 From: tmoldere at vub.ac.be (Tim Molderez) Date: Fri, 6 Jan 2017 16:16:23 +0100 Subject: 2017: Call for workshop, symposium & poster submissions Message-ID: ----------------------------------------------------------------------- 2017 : The Art, Science, and Engineering of Programming April 3-6, 2017, Brussels, Belgium http://2017.programming-conference.org ----------------------------------------------------------------------- We are excited to announce there will be 10 co-located events at the 2017 conference (and more to come!): - ELS 2017 - 10th European Lisp Symposium - Modularity 2017 Invited talks - International Symposium on Modularity - ACM Student Research Competition / 2017 Posters - LASSY 2017 - 2nd Workshop on Live Adaptation of Software SYstems - MOMO 2017 - 2nd Workshop on Modularity in Modelling - MoreVMs 2017 - 1st Workshop on Modern Language Runtimes, Ecosystems, and VMs - PASS 2017 - 1st Workshop on Programming Across the System Stack - PX 2017 - 2nd Workshop on Programming Experience - ProWeb 2017 - 1st Workshop on Programming Technology for the Future Web - Salon des Refus?s 2017 - 1st edition of the Salon des Refus?s workshop All co-located events will take place during April 3-4 2017. CFPs for each of these events are listed below. (apart from Modularity 2017, which is invitation-based) **************************************************************** ELS 2017 - 10th European Lisp Symposium Submissions: Mon 30 Jan 2017 Notifications: Mon 27 Feb 2017 http://2017.programming-conference.org/track/els-2017 **************************************************************** The purpose of the European Lisp Symposium is to provide a forum for the discussion and dissemination of all aspects of design, implementation and application of any of the Lisp and Lisp-inspired dialects, including Common Lisp, Scheme, Emacs Lisp, AutoLisp, ISLISP, Dylan, Clojure, ACL2, ECMAScript, Racket, SKILL, Hop and so on. We encourage everyone interested in Lisp to participate. The 10th European Lisp Symposium invites high quality papers about novel research results, insights and lessons learned from practical applications and educational perspectives. We also encourage submissions about known ideas as long as they are presented in a new setting and/or in a highly elegant way. Topics include but are not limited to: * Context-, aspect-, domain-oriented and generative programming * Macro-, reflective-, meta- and/or rule-based development approaches * Language design and implementation * Language integration, inter-operation and deployment * Development methodologies, support and environments * Educational approaches and perspectives * Experience reports and case studies ******************************************************************** ACM Student Research Competition / 2017 Posters Submissions: Mon 16 Jan 2017 http://2017.programming-conference.org/track/programming-posters ******************************************************************** The ACM Student Research Competition (SRC), sponsored by Microsoft Research, offers a unique forum for ACM student members at the undergraduate and graduate levels to present their original research before a panel of judges and conference attendees. The SRC gives visibility to up-and-coming young researchers, and offers them an opportunity to discuss their research with experts in their field, get feedback, and to help sharpen communication and networking skills. ACM?s SRC program covers expenses up to $500 for all students invited to an SRC. Please see our website for requirements and further details. ****************************************************************** LASSY 2017 - 2nd Workshop on Live Adaptation of Software SYstems Submissions: Fri 3 Feb 2017 Notifications: Fri 3 Mar 2017 http://2017.programming-conference.org/track/LASSY-2017-papers ****************************************************************** When developing current-day software systems, their deployment and usage environments should be considered carefully, in order to understand the adaptations those systems might need to undergo to interact with other systems and with their environment. Moreover, due to the portability, mobility and increasingly evolutionary nature of software systems, such adaptations should be enacted even while the system is running. Developing such software systems can prove challenging, and many seemingly different techniques to address this concern have been proposed over the last couple of years. The intention of the LASSY workshop is to congregate all topics relevant to dynamic adaptation and run-time evolution of software systems, ranging from a computer science perspective covering the domains of programming languages, model-driven software development, software and service composition, context-aware databases, software variability, requirements engineering, UI adaptation and other domains, to a human perspective covering sociological or ethical implications of dynamic software systems. The workshop provides a space for discussion and collaboration between researchers working on the problem of enabling live adaptations to software systems, across the development stack. Topics of Interest: * Design and Implementation of Live Adaptive Software Systems * Context-, aspect-, feature-, role- and agent-oriented programming * Context representation and discovery * Context-aware model-driven software development * Context-aware data management * Software variability and dynamic product lines * Self-adaptive, self-explanatory systems * Inconsistency management, verification, and validation * Middleware and Runtime of Live Adaptive Software Systems * Dynamic software evolution, upgrades and configuration * Dynamic software and service composition mechanisms * Dynamic software architecture and middleware approaches * Dynamic user interface adaptation and multimodal user interfaces * Impact and Assessment of Live Adaptive Software Systems * User acceptance and usability issues * Human, sociological, ethical and legal aspects * Privacy and security aspects of dynamic adaptability * Live adaptation in smart environments (e.g. smart rooms, smart robot cells, smart factories, smart cities) * Self-adaptation and emergence in SoS and CPSoS **************************************************************** MOMO 2017 - 2nd Workshop on Modularity in Modelling Abstract submissions (optional): Sun Jan 29 2017 Paper submissions: Sun Feb 5 2017 Notifications: Wed Feb 22 2017 http://www.momo2017.ece.mcgill.ca/cfp.htm **************************************************************** Extending the time-honored practice of separation of concerns, Model-Driven Engineering (MDE) promotes the use of separate models to address the various concerns in the development of complex software-intensive systems. The main objective is to choose the right level of abstraction to modularize a concern, specify its properties and reason about the system under development depending on stakeholder and development needs. While some of these models can be defined with a single modelling language, a variety of heterogeneous models and languages are typically used in the various phases of software development. Furthermore, Domain-Specific Modelling Languages designed to address particular concerns are also increasingly used. Despite the power of abstraction of modelling, models of real-world problems and systems quickly grow to such an extent that managing the complexity by using proper modularization techniques becomes necessary. As a result, many (standard) modelling notations have been extended with aspect-oriented mechanisms and advanced composition operators to support advanced separation of concerns, to combine (possibly heterogeneous) models modularizing different concerns, to execute an application based on modularized models, and to reason over global properties of modularized models. The Second International Modularity in Modelling Workshop brings together researchers and practitioners interested in the theoretical and practical challenges resulting from applying modularity, advanced separation of concerns, and advanced composition at the modelling level. It is intended to provide a forum for presenting new ideas and discussing the impact of the use of modularization in the context of MDE at different levels of abstraction. We are interested in submissions on all topics related to modularity and modelling including but not limited to: * Modularization Support in Modelling Languages and Tools * Model Interfaces * Homogeneous Model Composition Operators * Heterogeneous Model Composition Operators * Visualization of Modularized and Composed Models * Effects of Using Modularization and Composition in Modelling * On Verification and Validation * On Reuse * On the Model-Driven Software Development Process (Requirements Engineering, Software Architecture, Software Design, Implementation) * On Maintenance * Experience Reports / Empirical Evaluations of Applying Modularization and Composition in Modelling * Feature-Oriented, Aspect-Oriented and Concern-Oriented Modelling * Modularization support and composition operators for specific modelling notations * Modelling essential characteristics of specific (crosscutting) concerns * Multi-View Modelling: avoiding inconsistencies, avoiding Redundancies * Support for Detecting and/or Resolution of Feature Interactions * Domain-Specific Modelling * Modularization for Domain-Specific Languages * Composition for Domain-Specific Languages * Domain-specific Aspect Models ****************************************************************************** MoreVMs 2017 - 1st Workshop on Modern Language Runtimes, Ecosystems, and VMs Submissions: Wed 15 Feb 2017 Notifications: Wed 1 Mar 2017 http://2017.programming-conference.org/track/MoreVMs-2017-papers ****************************************************************************** The main goal of the workshop is to bring together both researchers and practitioners and facilitate effective sharing of their respective experiences and ideas on how languages and runtimes are utilized and where they need to improve further. We welcome presentation proposals in the form of extended abstracts discussing experiences, work-in-progress, as well as future visions from the academic as well as industrial perspective. Relevant topics include, but are definitely not limited to, the following: * Extensible VM design (compiler- or interpreter-based VMs) * Reusable runtime components (e.g. interpreters, garbage collectors, intermediate representations) * Static and dynamic compiler techniques * Techniques for compilation to high-level languages such as JavaScript * Runtimes and mechanisms for interoperability between languages * Tooling support (e.g. debugging, profiling, etc.) * Programming language development environments and virtual machines * Case studies of existing language implementations, virtual machines, and runtime components (e.g. design choices, tradeoffs, etc.) * Language implementation challenges and trade-offs (e.g. performance, completeness, etc.) * Surveys and applications usage reports to understand runtime usage in the wild * Surveys on frameworks and their impact on runtime usage * New research ideas on how we want to build languages in the future ************************************************************************** PASS 2017 - 1st Workshop on Programming Across the System Stack Submissions: Mon 13 Feb 2017 Notifications: Mon 27 Feb 2017 http://2017.programming-conference.org/track/PASS-2017#Call-for-Papers ************************************************************************** The landscape of computation platforms has changed dramatically in recent years. Emerging systems - such as wearable devices, smartphones, unmanned aerial vehicles, Internet of things, cloud computing servers, heterogeneous clusters, and data centers - pose a distinct set of system-oriented challenges ranging from data throughput, energy efficiency, security, real-time guarantees, to high performance. In the meantime, code quality, such as modularity or extensibility, remains a cornerstone in modern software engineering, bringing in crucial benefits such as modular reasoning, program understanding, and collaborative software development. Current methodologies and software development technologies should be revised in order to produce software to meet system-oriented goals, while preserving high internal code quality. The role of the Software Engineer is essential, having to be aware of the implications that each design, architecture and implementation decision has on the application system ecosystem. This workshop is driven by one fundamental question: How does internal code quality interact with system-oriented goals? We welcome both positive and negative responses to this question. An example of the former would be modular reasoning systems specifically designed to promote system-oriented goals, whereas an example of the latter would be anti-patterns against system-oriented goals during software development. Areas of interest include but are not limited to: * Energy-aware software engineering (e.g. energy efficiency models, energy efficiency as a quality attribute) * Modularity support (e.g., programming language design, development tools or verification) for applications in resource-constrained or real-time systems * Emerging platforms (e.g., Internet of Things and wearable devices) * Security support (e.g., compositional information flow, compositional program analysis) * Software architecture for reusability and adaptability in systems and their interactions with applications * Empirical studies (patterns and anti-patterns) on the relationship between internal code quality and system-oriented goals * Software engineering techniques to balance the trade-off between internal code quality and efficiency * Memory bloats and long-tail performance problems across modular boundaries * Program optimization across modular boundaries * Internal code quality in systems software * Reasoning across applications, compilers, and virtual machines **************************************************************** PX 2017 - 2nd Programming Experience Workshop Submissions: Sat 4 Feb 2017 Notifications: Mon 27 Feb 2017 http://programming-experience.org/px17 **************************************************************** Imagine a software development task: some sort of requirements and specification including performance goals and perhaps a platform and programming language. A group of developers head into a vast workroom. In that room they discover they need to explore the domain and the nature of potential solutions?they need exploratory programming. The Programming Experience Workshop is about what happens in that room when one or a couple of programmers sit down in front of computers and produce code, especially when it?s exploratory programming. Do they create text that is transformed into running behavior (the old way), or do they operate on behavior directly (?liveness?); are they exploring the live domain to understand the true nature of the requirements; are they like authors creating new worlds; does visualization matter; is the experience immediate, immersive, vivid and continuous; do fluency, literacy, and learning matter; do they build tools, meta-tools; are they creating languages to express new concepts quickly and easily; and curiously, is joy relevant to the experience? Correctness, performance, standard tools, foundations, and text-as-program are important traditional research areas, but the experience of programming and how to improve and evolve it are the focus of this workshop, and in this edition we would like to focus on exploratory programming. The technical topics include: * Exploratory programming * Live programming * Authoring * Representation of active content * Visualization * Navigation * Modularity mechanisms * Immediacy * Literacy * Fluency * Learning * Tool building * Language engineering ************************************************************************* ProWeb 2017 - 1st Workshop on Programming Technology for the Future Web Submissions: Wed 15 Feb 2017 Notifications: Wed 1 Mar 2017 http://2017.programming-conference.org/track/proweb-2017-papers ************************************************************************* Full-fledged web applications have become ubiquitous on desktop and mobile devices alike. Whereas ?responsive? web applications already offered a more desktop-like experience, there is an increasing demand for ?rich? web applications (RIAs) that offer collaborative and even off-line functionality ?Google docs being the prototypical example. Long gone are the days that web servers merely had to answer incoming HTTP request with a block of static HTML. Today?s servers react to a continuous stream of events coming from JavaScript applications that have been pushed to clients. As a result, application logic and data is increasingly distributed. Traditional dichotomies such as ?client vs. server? and ?offline vs. online? are fading. The 1st International Workshop on Programming Technology for the Future Web, or ProWeb17, is a forum for researchers and practitioners to share and discuss new technology for programming these and future evolutions of the web. We welcome submissions introducing programming technology (i.e., frameworks, libraries, programming languages, program analyses and development tools) for implementing web applications and for maintaining their quality over time, as well as experience reports about the use of state-of-the-art programming technology. Relevant topics include, but are not limited to: * Quality on the new web: static and dynamic program analyses; code, design test and process metrics; development and migration tools; automated testing and test generation; contract systems, type systems, and web service API conformance checking; ? * Hosting languages on the web: new runtimes; transpilation or compilation to JavaScript, WebAssembly, asm.js, ? * Designing languages for the web: multi-tier (or tierless) programming; reactive programming; frameworks for multi-tier or reactive programming on the web; ? * Distributed data sharing, replication and consistency: cloud types, CRDTs, eventual consistency, offline storage, peer-to-peer communication, ? * Security on the web: client-side and server-side security policies; policy enforcement; proxies and membranes; vulnerability detection; dynamic patching, ? * Surveys and case studies using state-of-the-art web technology (e.g., WebAssembly, WebSocket, LocalStorage, AppCache, ServiceWorkers, Meteor, deepstream.io, Angular.js, React and React Native, Swarm.js, Caja, TypeScript, Proxies, ClojureScript, Amber Smalltalk, Scala.js, ?) * Ideas on and experience reports about: how to reconcile the need for quality with the need for agility on the web; how to master and combine the myriad of tier-specific technologies required to develop a web application, ? * Position statements on what the future of the web will look like **************************************************************** Salon des Refus?s 2017 Submissions: Wed 1 Feb 2017 Notifications: Fri 17 Feb 2017 https://refuses.github.io **************************************************************** Salon des Refus?s (?exhibition of rejects?) was an 1863 exhibition of artworks rejected from the official Paris Salon. The jury of Paris Salon required near-photographic realism and classified works according to a strict genre hierarchy. Paintings by many, later famous, modernists such as ?douard Manet were rejected and appeared in what became known as the Salon des Refus?s. This workshop aims to be the programming language research equivalent of Salon des Refus?s. We provide a venue for exploring new ideas and new ways of doing computer science. Many interesting ideas about programming might struggle to find space in the modern programming language research community, often because they are difficult to evaluate using established evaluation methods (be it proofs, measurements or controlled user studies). As a result, new ideas are often seen as ?unscientific?. This workshop provides a venue where such interesting and thought-provoking ideas can be exposed to critical evaluation. Submissions that provoke interesting discussion among the program committee members will be published together with an attributed review that presents an alternative position, develops additional context or summarizes discussion from the workshop. This means of engaging with papers not just enables explorations of novel programming ideas, but also encourages new ways of doing computer science. Topics of interest The scope of the workshop is determined more by the format of submissions than by the specific area of programming language or computer science research that we are interested in. We welcome submissions in a format that makes it possible to think about programming in a new way, including, but not limited to: * Thought experiments ? we believe that thought experiments, analogies and illustrative metaphors can provide novel insights and inspire fruitful programming language ideas. * Experimentation ? we find prejudices in favour of theory, as far back as there is institutionalized science, but programming can often be seen more as experimentation than as theorizing. We welcome interesting experiments even if there is yet no overarching theory that explains why they happened. * Paradigms ? all scientific work is rooted in a scientific paradigm that frame what questions can be asked. We encourage submissions that reflect on existing paradigms or explore alternative scientific paradigms. * Metaphors, myths and analogies ? any description of formal, mathematical, quantitative or even poetical nature still represents just an analogy. We believe that fruitful ideas can be learned from less common forms of analogies as well as from the predominant, formal and mathematical ones. * From jokes to science fiction ? a story or an artistic performance may explore ideas and spark conversations that provide crucial inspiration for development of new computer science thinking. From kwpolska at gmail.com Sun Jan 8 14:34:43 2017 From: kwpolska at gmail.com (Chris Warrick) Date: Sun, 8 Jan 2017 20:34:43 +0100 Subject: Nikola v7.8.2 is out! Message-ID: On behalf of the Nikola team, I am pleased to announce the immediate availability of Nikola v7.8.2. It adds a ton of new features, while also fixing some bugs. Key Changes =========== * A rewrite of all taxonomies (tags, categories, sections, etc.) in a generic fashion, allowing for much greater flexibility (by Felix Fontein) ? adds new settings, enables new features (``CREATE_ARCHIVE_NAVIGATION``) and customizability * Automatic cration of ``year/month/day`` directory structures (``NEW_POST_DATE_PATH``) * Ability to sort posts from within templates (``sort_posts``) * API changes for post compilers (new ``compile``, ``compile_string`` functions) * Addition of a generator meta tag to default themes ? we hope you do not mind a bit of promotion for Nikola? What is Nikola? =============== Nikola is a static site and blog generator, written in Python. It can use Mako and Jinja2 templates, and input in many popular markup formats, such as reStructuredText and Markdown ? and can even turn Jupyter (IPython) Notebooks into blog posts! It also supports image galleries, and is multilingual. Nikola is flexible, and page builds are extremely fast, courtesy of doit (which is rebuilding only what has been changed). Find out more at the website: https://getnikola.com/ Downloads ========= Install using `pip install Nikola` or download tarballs on GitHub and PyPI: https://github.com/getnikola/nikola/releases/tag/v7.8.2 https://pypi.python.org/pypi/Nikola/7.8.2 Changes ======= **Minor API change:** The ``compile_string`` compiler method (partially internal) now takes a post argument and returns between two and four values, adding ``shortcode_deps`` and shortcode support. See issues #2623 and #2624. Features -------- * Add meta generator tag to default templates to promote Nikola (Issue #2619) * Add ``nikola new_post -d`` and ``NEW_POST_DATE_PATH`` to allow automatic creation of year/month/day (date-based) directory structures (Issue #2513) * Allow enabling pretty URLs with per-post setting (Issue #2613) * Add a ``sort_posts`` function (available as Jinja filter in global context), which allows general-purpose timeline sorting (Issue #2602) * Allow creating archive navigation (Issue #1639) * Accept a ``page`` argument for taxonomy paths (Issue #2585) * Query strings in magic links are passed as keyword arguments to path handlers (via Issue #2580) * Accept arbitrary arguments to path handlers (via Issue #2580) * Added new ``typogrify_oldschool`` filter (Issue #2574) * Improving handling of .dep files, and allowing compilers to specify additional targets for the ``render_posts`` task (Issue #2536) * ``render_template`` and ``generic_renderer`` can now create HTML fragments. * Allow posts to set custom ``URL_TYPE`` by using the ``url_type`` meta tag (useful for HTML fragments inserted using JavaScript) * Plugins can depend on other plugins being installed (Issue #2533) * The destination folder in ``POSTS`` and ``PAGES`` can now be translated (Issue #2116) * Pass ``post`` object and ``lang`` to post compilers (Issue #2531) * Pass ``url_type`` into template's context. * Make thumbnail naming configurable with ``IMAGE_THUMBNAIL_FORMAT``. * There is a new plugin category ``Taxonomy`` which allows to easily create new taxonomies. All of the existing taxonomies (authors, archives, indexes, page index, sections, tags, and categories) have been converted to the new system. (Issue #2107) * Added ``CATEGORIES_INDEX_PATH``, similar to ``TAGS_INDEX_PATH``. (Issue #2567) * Made ``INDEX_PATH``, ``RSS_PATH`` and ``AUTHOR_PATH`` translatable. (Issue #1914) * Added setting ``SHOW_INDEX_PAGE_NAVIGATION`` which enables a basic page navigation for indexes. (Issue #2299) * Added settings ``DISABLE_INDEXES_PLUGIN_INDEX_AND_ATOM_FEED`` and ``DISABLE_INDEXES_PLUGIN_RSS_FEED`` to disable specific parts of the ``classify_indexes`` taxonomy plugin. (Issue #2591) Bugfixes -------- * Work around conflicts between posts and sections trying to render index.html files (via Issue #2613) * Make ``AUTHOR_PAGES_ARE_INDEXES`` really work (Issue #2600) * WordPress importer now correctly handles & etc. in tags. (Issue #2557) * If ``CODE_COLOR_SCHEME`` is empty, don?t generate ``code.css`` (Issue #2597) * Don?t warn about ``nikolademo`` DISQUS account when comments are disabled (Issue #2588) * Make ``data`` from global context available to templated shortcodes as ``global_data`` (Issue #2488) * Don't crash if plugins is a file (Issue #2539) * Don't mangle bare ``#`` links (Issue #2553) * ``generic_index_renderer`` now always produces output. It previously did not when the post list was empty and ``INDEXES_STATIC == False``. (via Issue #2579) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: From bryanv at continuum.io Mon Jan 9 14:08:30 2017 From: bryanv at continuum.io (Bryan Van de Ven) Date: Mon, 9 Jan 2017 13:08:30 -0600 Subject: ANN: Bokeh 0.12.4 Released Message-ID: Hi all, On behalf of the Bokeh team, I am pleased to announce the release of version 0.12.4 of Bokeh! Please see the announcement post at: https://bokeh.github.io/blog/2017/1/6/release-0-12-4/ which has more information as well as live demonstrations. If you are using Anaconda/miniconda, you can install it with conda: conda install -c bokeh bokeh Alternatively, you can also install it with pip: pip install bokeh Full information including details about how to use and obtain BokehJS are at: http://bokeh.pydata.org/en/0.12.4/docs/installation.html Issues, enhancement requests, and pull requests can be made on the Bokeh Github page: https://github.com/bokeh/bokeh Documentation is available at http://bokeh.pydata.org/en/0.12.4 There are over 200 total contributors to Bokeh and their time and effort help make Bokeh such an amazing project and community. Thank you again for your contributions. Finally (as always), for questions, technical assistance or if you're interested in contributing, questions can be directed to the Bokeh mailing list: bokeh at continuum.io or the Gitter Chat room: https://gitter.im/bokeh/bokeh Thanks, Bryan Van de Ven From exarkun at twistedmatrix.com Mon Jan 9 12:58:24 2017 From: exarkun at twistedmatrix.com (Jean-Paul Calderone) Date: Mon, 9 Jan 2017 12:58:24 -0500 Subject: Announcing txAWS 0.2.3.1 Message-ID: I've just release txAWS 0.2.3.1. txAWS is a library for interacting with Amazon Web Services (AWS) using Twisted. AWSServiceEndpoint's ssl_hostname_verification's parameter now defaults to True instead of False. This affects all txAWS APIs which issue requests to AWS endpoints. For any application which uses the default AWSServiceEndpoints, the server's TLS certificate will now be verified. This resolves a security issue in which txAWS applications were vulnerable to man-in-the-middle attacks which could either steal sensitive information or, possibly, alter the AWS operation requested. The new release is available on PyPI in source and wheel forms. You can also find txAWS at its new home on github, . Special thanks to Least Authority Enterprises () for sponsoring the work to find and fix this issue and to publish this new release. Jean-Paul From donald at python.org Tue Jan 10 08:27:21 2017 From: donald at python.org (Donald Stufft) Date: Tue, 10 Jan 2017 08:27:21 -0500 Subject: Announcement: TLSv1.2 will become mandatory in the future for Python.org Sites Message-ID: <1B1B29CD-AA4E-47C0-89A8-2748D5A14FC3@python.org> Fastly has announced plans to disable TLSv1.0 and TLSv1.1 on their CDN endpoints which will include PyPI (as well as other Python properties). You can see their timeline at https://www.fastly.com/blog/phase-two-our-tls-10-and-11-deprecation-plan. There are two hard cut off dates to remember: * April 30, 2017, which is when any Python.org site you see that does *not* have an EV certificate that is hosted by Fastly will no longer support TLSv1.0 and TLSv1.1 (testpypi.python.org, test.pypi.org, files.pythonhosted.org, etc). * June 30, 2018, which is when any Python.org site you see that has an EV certificate that is hosted by Fastly will no longer support TSLv1.0 and TLSv1.1 (pypi.python.org, pypi.org, etc). I am going to see about possibly organizing some scheduled "brown outs" of TLSv1.0 and TLSv1.1 prior to the cut off dates to try and help folks find places that will need updates. Any scheduled brownouts will be posted to status.python.org prior to happening. Looking at the download numbers, the absolute largest driver of TLSv1.0 and TLSv1.1 traffic to PyPI are old versions of pip or other clients where I cannot tell the OS that they are being run on. Past that, macOS is going to be the largest casualty since their system Python does not support TLSv1.2 yet in any version of their OS. If you have a Python and you want to check to see if it supports TLSv1.2 or not, the easiest way to do that is by running: python2 -c "import urllib2,json; print(json.loads(urllib2.urlopen('https://www.howsmyssl.com/a/check').read())['tls_version'])" OR python3 -c "import urllib.request,json; print(json.loads(urllib.request.urlopen('https://www.howsmyssl.com/a/check').read())['tls_version'])" If you get something other than TLS 1.2, then I suggest making plans to deal with the inevitable breakage which may start occurring on or before April 30, 2017. From teoliphant at gmail.com Thu Jan 12 02:25:29 2017 From: teoliphant at gmail.com (Travis Oliphant) Date: Thu, 12 Jan 2017 01:25:29 -0600 Subject: ANN: AnacondaCON February 7-9, Austin TX --- Python powered Open Data Science Conference Message-ID: AnacondaCON February 7-9, Austin Texas http://anacondacon17.io 3-day Anaconda Open Data Science User Conference celebrating a strong Python success story. Hello everyone, It has been 5 years since Peter Wang and I started Continuum Analytics with the objective of expanding the commercial adoption of Python for data-science, quantitative, computational, and numerical computing. Thanks to the amazing community and my colleagues at Continuum we've seen that objective come to fruition and company after company is choosing Python as their forward looking numerical computing modeling and data-science language. We created Anaconda to make it easy for individuals and organizations to adopt the rich suite of tools and libraries that are commonly used by scientists, engineers, and mathematicians. As Anaconda has lowered the barrier for people to adopt the open data science software stack we've seen a significant increase in use by people who previously were unlikely to move beyond Excel, and organizations who are recognizing the kind of value that a strategic investment in Python can bring them. Nearly 8 million people have downloaded Anaconda this year many of whom are using Python for the first time (and choosing Python 3.X). It's been a dream come true to see all of our early efforts around SciPy, NumPy, and Python come to fruition in the enterprise. It's been an incredible journey and is something the Python community can and should celebrate. With that background I am excited to announce AnacondaCON, a 3 day Anaconda user conference happening February 7-9 in Austin Texas. We currently have 2-for-1 pricing until January 16th (2 tickets for $999). We have an amazing line up of speakers from industry, government, academia and, of course, Continuum. https://anacondacon17.io/speakers/ Peter and I will both be speaking there. I will be speaking about the future of open data science including what community-oriented open-source technologies we specifically will be working on and contributing to that continue the success of numpy, scipy, pandas, conda, numba, bokeh, dask, spyder, holoviews, phosphorjs, jupyter, and more. I will also be discussing some ideas we are pursuing on the future of array computing for Python 3.X and how to build a substructure for vector computing that integrates better with the broader Python ecosystem and is inspired by and can use the typing hints becoming popular in Python 3.X. Python's future in technical computing and data science has never been brighter and AnacondaCON is a great opportunity to connect with an interesting segment of this larger community and catch up with others interested in enterprise adoption of Python for data science and numerical / technical computing. I really hope to see you there. Best, Travis Oliphant From info at wingware.com Thu Jan 12 08:48:29 2017 From: info at wingware.com (Wingware) Date: Thu, 12 Jan 2017 08:48:29 -0500 Subject: Wing IDE 6.0.1 released Message-ID: <5877892D.4080407@wingware.com> Hi, We've just released Wing IDE 6.0.1 which improves remote host configuration, adds remote development support for 32-bit Linux and older 64-bit Linux systems, fixes stability problems affecting some users, and makes many other improvements. For details on this release, see the change log at http://wingware.com/pub/wingide/6.0.1/CHANGELOG.txt Wing IDE 6 is the latest major release of Wingware's Python IDE that adds many new features, introduces a new annual license option, and makes some changes to the product line. New Features * Improved Multiple Selections: Quickly add selections and edit them all at once * Easy Remote Development: Work seamlessly on remote Linux, OS X, and Raspberry Pi systems * Debugging in the Python Shell: Reach breakpoints and exceptions in (and from) the Python Shell * Recursive Debugging: Debug code invoked in the context of stack frames that are already being debugged * PEP 484 and PEP 526 Type Hinting: Inform Wing's static analysis engine of types it cannot infer * Support for Python 3.6 and Stackless 3.4: Use async and other new language features * Optimized debugger: Run faster, particularly in multi-process and multi-threaded code * Support for OS X full screen mode: Zoom to a virtual screen, with auto-hiding menu bar * Added a new One Dark color palette: Enjoy the best dark display style yet * Updated French and German localizations: Thanks to Jean Sanchez, Laurent Fasnacht, and Christoph Heitkamp For a much more detailed overview of new features see the release notice at http://wingware.com/news/2017-01-10 Annual Use License Option Wing 6 adds the option of purchasing a lower-cost expiring annual license for Wing IDE Pro. An annual license includes access to all available Wing IDE versions while it is valid, and then ceases to function if it is now renewed. Pricing for annual licenses is US$ 179/user for Commercial Use and US$ 69/user for Non-Commercial Use. Perpetual licenses for Wing IDE will continue to be available at the same pricing. The cost of extending Support+Upgrades subscriptions on Non-Commercial Use perpetual licenses for Wing IDE Pro has also been dropped from US$ 89 to US$ 39 per user. For details, see https://wingware.com/store/purchase Wing Personal is Free Wing IDE Personal is now free and no longer requires a license to run. It now also includes the Source Browser, PyLint, and OS Commands tools, and supports the scripting API and Perspectives. However, Wing Personal does not include Wing Pro's advanced editing, debugging, testing and code management features, such as remote host access, refactoring, find uses, version control, unit testing, interactive debug probe, multi-process and child process debugging, move program counter, conditional breakpoints, debug watch, framework-specific support (for matplotlib, Django, and others), find symbol in project, and other features. Links Release notice: http://wingware.com/news/2017-01-10 Free trial: http://wingware.com/wingide/trial Downloads: http://wingware.com/downloads Feature list: http://wingware.com/wingide/features Buy: http://wingware.com/store/purchase Upgrade: https://wingware.com/store/upgrade Questions? Don't hesitate to email us at support at wingware.com. Thanks, -- Stephan Deibel Wingware | Python IDE The Intelligent Development Environment for Python Programmers wingware.com From krzysztof.laskowski.1986 at gmail.com Thu Jan 12 16:53:39 2017 From: krzysztof.laskowski.1986 at gmail.com (Krzysztof Laskowski) Date: Thu, 12 Jan 2017 22:53:39 +0100 Subject: prophy 1.0.0 released Message-ID: Hi All, I'd like to announce prophy 1.0.0, the serialization framework. Like protobuf, thrift, capnproto, flatbuffers or SBE, it comes with: - protocol definition language, - wire-format specification, - compiler which generates codecs, - runtime libraries for codecs. Codecs come in Python and C++ languages. Protocol/wire-format follows C language struct with natural alignment, possibly with flexible arrays at the end, so performance of encoding/decoding is expected to be rather good, although protocol is quite limited. Embedded systems is where such resource effective protocol could be helpful. License: MIT Code: https://github.com/aurzenligl/prophy Docs: http://prophy.readthedocs.io/en/latest/ Pypi: https://pypi.python.org/pypi/prophy Issues: https://github.com/aurzenligl/prophy/issues I'm open to feedback and suggestions, which I'd happily receive via mail or github issues. Best Regards, Krzysztof Laskowski From kwpolska at gmail.com Fri Jan 13 04:25:57 2017 From: kwpolska at gmail.com (Chris Warrick) Date: Fri, 13 Jan 2017 10:25:57 +0100 Subject: Nikola v7.8.3 is out! (emergency bugfix release) Message-ID: <062d52eb-cefa-9c9e-1631-6e13bfc5fad1@gmail.com> On behalf of the Nikola team, I am pleased to announce the immediate availability of Nikola v7.8.3. This is an emergency bugfix release, which fixes a bug that prevented ``nikola new_page`` from working. There has also been a minor change to post sorting order (won?t affect most sites). The wheel packages have also been fixed (they now exist for Python 2 and 3, with correct doit versioning). What is Nikola? =============== Nikola is a static site and blog generator, written in Python. It can use Mako and Jinja2 templates, and input in many popular markup formats, such as reStructuredText and Markdown ? and can even turn Jupyter (IPython) Notebooks into blog posts! It also supports image galleries, and is multilingual. Nikola is flexible, and page builds are extremely fast, courtesy of doit (which is rebuilding only what has been changed). Find out more at the website: https://getnikola.com/ Downloads ========= Install using `pip install Nikola` or download tarballs on GitHub and PyPI: https://github.com/getnikola/nikola/releases/tag/v7.8.3 https://pypi.python.org/pypi/Nikola/7.8.3 Changes ======= Features -------- * Sort posts chronologically with one unified function (easier to change). (Issue #2627) * Sort posts in the following order (most important last): source path (A-Z), title (A-Z), date (reverse chronological order), priority meta number (descending). (Issue #2627) Bugfixes -------- * Fix a bug that prevents ``nikola new_page`` from working (Issue #2631) -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 455 bytes Desc: OpenPGP digital signature URL: From charlesr.harris at gmail.com Sun Jan 15 18:43:41 2017 From: charlesr.harris at gmail.com (Charles R Harris) Date: Sun, 15 Jan 2017 16:43:41 -0700 Subject: NumPy 1.12.0 release Message-ID: Hi All, I'm pleased to announce the NumPy 1.12.0 release. This release supports Python 2.7 and 3.4-3.6. Wheels for all supported Python versions may be downloaded from PiPY , the tarball and zip files may be downloaded from Github . The release notes and files hashes may also be found at Github . NumPy 1.12.0rc 2 is the result of 418 pull requests submitted by 139 contributors and comprises a large number of fixes and improvements. Among the many improvements it is difficult to pick out just a few as standing above the others, but the following may be of particular interest or indicate areas likely to have future consequences. * Order of operations in ``np.einsum`` can now be optimized for large speed improvements. * New ``signature`` argument to ``np.vectorize`` for vectorizing with core dimensions. * The ``keepdims`` argument was added to many functions. * New context manager for testing warnings * Support for BLIS in numpy.distutils * Much improved support for PyPy (not yet finished) Enjoy, Chuck From h.goebel at goebel-consult.de Sun Jan 15 16:15:31 2017 From: h.goebel at goebel-consult.de (Hartmut Goebel) Date: Sun, 15 Jan 2017 22:15:31 +0100 Subject: [ANN] PyInstaller 3.2.1 Message-ID: <69f768fb-73c5-8bd7-d6f5-6c8dafbed524@goebel-consult.de> Hello, on behalf of the PyInstaller development team I'm happy to announce PyInstaller 3.2.1, the long awaited bug-fix release http://www.pyinstaller.org Thanks for all those who contributed questions, bug-reports or pull-requests. === What it is === PyInstaller bundles a Python application and all its dependencies into a single package. The user can run the packaged app without installing a Python interpreter or any modules. PyInstaller reads a Python script written by you. It analyzes your code to discover every other module and library your script needs in order to execute. Then it collects copies of all those files ? including the active Python interpreter! ? and puts them with your script in a single folder, or optionally in a single executable file. PyInstaller is tested against Windows, Mac OS X, and Linux. However, it is not a cross-compiler: to make a Windows app you run PyInstaller in Windows; to make a Linux app you run it in Linux, etc. PyInstaller has been used successfully with AIX, Solaris, and FreeBSD, but is not tested against them. === Installation === PyInstaller can be installed from PyPi using pip install pyinstaller === Changes === - Many bug fixes and internal enhancements, the most important ones are: - (Windows) Fix additional dependency on the msvcrt10.dll (#1974) - (OS X) PyQt5 packaging issues on MacOS (#1874) - (Bootloader) fix segfaults (#2176) - Some new, fixed or enhanced hooks. The full changelog for this release can be found at: https://pyinstaller.readthedocs.io/en/v3.2.1/CHANGES.html === Feedback === We're eager to listen to your feedback on using PyInstaller: Bug tracker: https://github.com/pyinstaller/pyinstaller/issues Mailing list: http://groups.google.com/group/PyInstaller -- Sch?nen Gru? Hartmut Goebel Dipl.-Informatiker (univ), CISSP, CSSLP, ISO 27001 Lead Implementer Information Security Management, Security Governance, Secure Software Development Goebel Consult, Landshut http://www.goebel-consult.de Blog: http://www.goebel-consult.de/blog/bewertung-pgp-verschlusselung-bei-web.de-und-gmx Kolumne: http://www.cissp-gefluester.de/2012-01-in-die-cloud-in-die-cloud-aber-wo-soll-die-sein From info at egenix.com Mon Jan 16 06:35:14 2017 From: info at egenix.com (eGenix Team: M.-A. Lemburg) Date: Mon, 16 Jan 2017 12:35:14 +0100 Subject: =?UTF-8?Q?ANN:_Python_Meeting_D=c3=bcsseldorf_-_18.01.2017?= Message-ID: [This announcement is in German since it targets a local user group meeting in D?sseldorf, Germany] ________________________________________________________________________ ANK?NDIGUNG Python Meeting D?sseldorf http://pyddf.de/ Ein Treffen von Python Enthusiasten und Interessierten in ungezwungener Atmosph?re. Mittwoch, 18.01.2017, 18:00 Uhr Raum 1, 2.OG im B?rgerhaus Stadtteilzentrum Bilk D?sseldorfer Arcaden, Bachstr. 145, 40217 D?sseldorf Diese Nachricht ist auch online verf?gbar: http://www.egenix.com/company/news/Python-Meeting-Duesseldorf-2017-01-18 ________________________________________________________________________ NEUIGKEITEN * Bereits angemeldete Vortr?ge: Charlie Clark "Kurze Einf?hrung in openpyxl und Pandas" Jochen Wersd?rfer "CookieCutter" Marc-Andre Lemburg "Optimierung in Python mit PuLP" Weitere Vortr?ge k?nnen gerne noch angemeldet werden: info at pyddf.de * Startzeit und Ort: Wir treffen uns um 18:00 Uhr im B?rgerhaus in den D?sseldorfer Arcaden. Das B?rgerhaus teilt sich den Eingang mit dem Schwimmbad und befindet sich an der Seite der Tiefgarageneinfahrt der D?sseldorfer Arcaden. ?ber dem Eingang steht ein gro?es "Schwimm' in Bilk" Logo. Hinter der T?r direkt links zu den zwei Aufz?gen, dann in den 2. Stock hochfahren. Der Eingang zum Raum 1 liegt direkt links, wenn man aus dem Aufzug kommt. Google Street View: http://bit.ly/11sCfiw ________________________________________________________________________ EINLEITUNG Das Python Meeting D?sseldorf ist eine regelm??ige Veranstaltung in D?sseldorf, die sich an Python Begeisterte aus der Region wendet: * http://pyddf.de/ Einen guten ?berblick ?ber die Vortr?ge bietet unser YouTube-Kanal, auf dem wir die Vortr?ge nach den Meetings ver?ffentlichen: * http://www.youtube.com/pyddf/ Veranstaltet wird das Meeting von der eGenix.com GmbH, Langenfeld, in Zusammenarbeit mit Clark Consulting & Research, D?sseldorf: * http://www.egenix.com/ * http://www.clark-consulting.eu/ ________________________________________________________________________ PROGRAMM Das Python Meeting D?sseldorf nutzt eine Mischung aus (Lightning) Talks und offener Diskussion. Vortr?ge k?nnen vorher angemeldet werden, oder auch spontan w?hrend des Treffens eingebracht werden. Ein Beamer mit XGA Aufl?sung steht zur Verf?gung. (Lightning) Talk Anmeldung bitte formlos per EMail an info at pyddf.de ________________________________________________________________________ KOSTENBETEILIGUNG Das Python Meeting D?sseldorf wird von Python Nutzern f?r Python Nutzer veranstaltet. Um die Kosten zumindest teilweise zu refinanzieren, bitten wir die Teilnehmer um einen Beitrag in H?he von EUR 10,00 inkl. 19% Mwst, Sch?ler und Studenten zahlen EUR 5,00 inkl. 19% Mwst. Wir m?chten alle Teilnehmer bitten, den Betrag in bar mitzubringen. ________________________________________________________________________ ANMELDUNG Da wir nur f?r ca. 20 Personen Sitzpl?tze haben, m?chten wir bitten, sich per EMail anzumelden. Damit wird keine Verpflichtung eingegangen. Es erleichtert uns allerdings die Planung. Meeting Anmeldung bitte formlos per EMail an info at pyddf.de ________________________________________________________________________ WEITERE INFORMATIONEN Weitere Informationen finden Sie auf der Webseite des Meetings: http://pyddf.de/ Mit freundlichen Gr??en, -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, Jan 16 2017) >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> Python Database Interfaces ... http://products.egenix.com/ >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/ From larry at hastings.org Tue Jan 17 03:40:39 2017 From: larry at hastings.org (Larry Hastings) Date: Tue, 17 Jan 2017 00:40:39 -0800 Subject: [RELEASED] Python 3.4.6 and Python 3.5.3 are now available Message-ID: On behalf of the Python development community and the Python 3.4 and Python 3.5 release teams, I'm delighted to announce the availability of Python 3.4.6 and Python 3.5.3. Python 3.4 is now in "security fixes only" mode. This is the final stage of support for Python 3.4. Python 3.4 now only receives security fixes, not bug fixes, and Python 3.4 releases are source code only--no more official binary installers will be produced. Python 3.5 is still in active "bug fix" mode. Python 3.5.3 contains many incremental improvements over Python 3.5.2. There were literally no code changes between rc1 and final for either release. The only change--apart from the necessary updates from "rc1" to final--was a single copyright notice update for one of the OS X ".plist" property list files in 3.5.3 final. You can find Python 3.5.3 here: https://www.python.org/downloads/release/python-353/ And you can find Python 3.4.6 here: https://www.python.org/downloads/release/python-346/ Best wishes, //arry/ From anthony.tuininga at gmail.com Sun Jan 22 00:02:35 2017 From: anthony.tuininga at gmail.com (Anthony Tuininga) Date: Sat, 21 Jan 2017 22:02:35 -0700 Subject: cx_Freeze repository moved Message-ID: All, I have just moved the cx_Freeze repository from BitBucket to GitHub. The new location is https://github.com/anthony-tuininga/cx_Freeze If anyone has a GitHub account and wishes their contributions to be recognised, please send me an e-mail with your GitHub account and I will update the link. The issues have been migrated from BitBucket to GitHub. The web page is now using GitHub pages and can be found here. Older links will be updated over the coming days with forwarding links. https://anthony-tuininga.github.io/cx_Freeze/ Anthony From georg at python.org Sun Jan 22 16:26:41 2017 From: georg at python.org (Georg Brandl) Date: Sun, 22 Jan 2017 22:26:41 +0100 Subject: Pygments 2.2 released Message-ID: <3856edb8-cc67-d903-a84e-594e33efc66e@python.org> I'm happy to announce the release of Pygments 2.2. Pygments is a generic syntax highlighter written in Python. There is a again lots of news in the 2.2 release, please have a look at the changelog . There are about 20 new languages supported, and a few other new features. Report bugs and feature requests in the issue tracker: . Thanks go to all the contributors of these lexers, and to all those who reported bugs and waited patiently for this release. Download it from , or look at the demonstration at . Enjoy, Georg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 195 bytes Desc: OpenPGP digital signature URL: From i.tkomiya at gmail.com Sun Jan 22 21:40:57 2017 From: i.tkomiya at gmail.com (Komiya Takeshi) Date: Mon, 23 Jan 2017 11:40:57 +0900 Subject: Sphinx-1.5.2 has been released Message-ID: Hi all, I'm delighted to announce the release of Sphinx 1.5.2, now available on the Python package index at . It includes about 5 new feature and 28 bug fixes for the 1.5.1 release series. For the full changelog, go to . Thanks to all collaborators and contributers! What is it? =========== Sphinx is a tool that makes it easy to create intelligent and beautiful documentation for Python projects (or other documents consisting of multiple reStructuredText source files). Website: http://sphinx-doc.org/ IRC: #sphinx-doc on irc.freenode.net Enjoy! -- Takeshi KOMIYA From opensoruce at ronnypfannschmidt.de Sun Jan 22 16:19:04 2017 From: opensoruce at ronnypfannschmidt.de (opensoruce at ronnypfannschmidt.de) Date: Sun, 22 Jan 2017 22:19:04 +0100 Subject: pytest 3.0.6 released Message-ID: <20170122221904.3ba0da27@ronny-rh-work-nix> pytest-3.0.6 ============ pytest 3.0.6 has just been released to PyPI. This is a bug-fix release, being a drop-in replacement. To upgrade:: pip install --upgrade pytest The full changelog is available at http://doc.pytest.org/en/latest/changelog.html. Thanks to all who contributed to this release, among them: * Andreas Pelme * Bruno Oliveira * Dmitry Malinovsky * Eli Boyarski * Jakub Wilk * Jeff Widman * Lo?c Est?ve * Luke Murphy * Miro Hron?ok * Oscar Hellstr?m * Peter Heatwole * Philippe Ombredanne * Ronny Pfannschmidt * Rutger Prins * Stefan Scherfke Happy testing, The pytest Development Team From randy at thesyrings.us Wed Jan 25 10:28:46 2017 From: randy at thesyrings.us (Randy Syring) Date: Wed, 25 Jan 2017 10:28:46 -0500 Subject: Proposal to discontinue pymssql in favor of pyodbc Message-ID: <72739a65-6a29-7dee-da72-13dc20f1cfaf@thesyrings.us> There is a proposal open to discontinue pymssql development and point people towards pyodbc. If you have any skin in that game and want to comment, please visit the issue: https://github.com/pymssql/pymssql/issues/477 Thanks. *Randy Syring* Husband | Father | Redeemed Sinner /"For what does it profit a man to gain the whole world and forfeit his soul?" (Mark 8:36 ESV)/ From paul.l.kehrer at gmail.com Fri Jan 27 10:27:39 2017 From: paul.l.kehrer at gmail.com (Paul Kehrer) Date: Fri, 27 Jan 2017 07:27:39 -0800 Subject: PyCA cryptography 1.7.2 released Message-ID: PyCA cryptography 1.7.2 has been released to PyPI. cryptography is a package which provides cryptographic recipes and primitives to Python developers. Our goal is for it to be your "cryptographic standard library". We support Python 2.6-2.7, Python 3.3+, and PyPy. This release updates the version of OpenSSL shipping in the Windows and macOS wheels to 1.0.2k. There are no other changes. -Paul Kehrer (reaperhulk) From denis.akhiyarov at gmail.com Mon Jan 30 02:13:07 2017 From: denis.akhiyarov at gmail.com (Denis Akhiyarov) Date: Sun, 29 Jan 2017 23:13:07 -0800 (PST) Subject: Python for .NET (pythonnet) v2.2.2 with Python 3.6 support Message-ID: <4ce02706-08c0-416d-a452-5a31efb216bd@googlegroups.com> Download from PYPI using pip or from Anaconda using conda: https://pypi.python.org/pypi/pythonnet/2.2.2 https://anaconda.org/pythonnet/pythonnet From faltet at gmail.com Sun Jan 29 08:07:48 2017 From: faltet at gmail.com (Francesc Alted) Date: Sun, 29 Jan 2017 14:07:48 +0100 Subject: ANN: numexpr 2.6.2 released! Message-ID: ========================= Announcing Numexpr 2.6.2 ========================= What's new ========== This is a maintenance release that fixes several issues, with special emphasis in keeping compatibility with newer NumPy versions. Also, initial support for POWER processors is here. Thanks to Oleksandr Pavlyk, Alexander Shadchin, Breno Leitao, Fernando Seiti Furusato and Antonio Valentino for their nice contributions. In case you want to know more in detail what has changed in this version, see: https://github.com/pydata/numexpr/blob/master/RELEASE_NOTES.rst What's Numexpr ============== Numexpr is a fast numerical expression evaluator for NumPy. With it, expressions that operate on arrays (like "3*a+4*b") are accelerated and use less memory than doing the same calculation in Python. It wears multi-threaded capabilities, as well as support for Intel's MKL (Math Kernel Library), which allows an extremely fast evaluation of transcendental functions (sin, cos, tan, exp, log...) while squeezing the last drop of performance out of your multi-core processors. Look here for a some benchmarks of numexpr using MKL: https://github.com/pydata/numexpr/wiki/NumexprMKL Its only dependency is NumPy (MKL is optional), so it works well as an easy-to-deploy, easy-to-use, computational engine for projects that don't want to adopt other solutions requiring more heavy dependencies. Where I can find Numexpr? ========================= The project is hosted at GitHub in: https://github.com/pydata/numexpr You can get the packages from PyPI as well (but not for RC releases): http://pypi.python.org/pypi/numexpr Share your experience ===================== Let us know of any bugs, suggestions, gripes, kudos, etc. you may have. Enjoy data! -- Francesc Alted From laurent.pointal at laposte.net Sat Jan 28 10:27:55 2017 From: laurent.pointal at laposte.net (Laurent Pointal) Date: Sat, 28 Jan 2017 16:27:55 +0100 Subject: Update to Python 3 Cheat Sheet Message-ID: <2454084.IAB1zqCHNc@litchi.pointalnet.home> Hi, I updated the cheat sheet on the aesthetic side. Parts bloc and their title are now more easily identified with colors (but its nice with B&W printing too). French and german versions have also been updated. See https://perso.limsi.fr/pointal/python:memento A+ L.Pointal. From vinay_sajip at yahoo.co.uk Sun Jan 29 13:53:44 2017 From: vinay_sajip at yahoo.co.uk (Vinay Sajip) Date: Sun, 29 Jan 2017 18:53:44 +0000 (UTC) Subject: ANN: A new version (0.4.0) of python-gnupg has been released. References: <1452661764.26048248.1485716024551.ref@mail.yahoo.com> Message-ID: <1452661764.26048248.1485716024551@mail.yahoo.com> A new version of the Python module which wraps GnuPG has been released. What Changed? ============= This is an enhancement and bug-fix release, and all users are encouraged to upgrade. See the project website [1] for more information. Brief summary: * Added support for ``KEY_CONSIDERED`` in more places - encryption / decryption, signing, key generation and key import. * Partial fix for #32 (GPG 2.1 compatibility). Unfortunately, better support cannot be provided at this point, unless there are certain changes (relating to pinentry popups) in how GPG 2.1 works. * Fixed #60: An IndexError was being thrown by ``scan_keys()``. * Ensured that utf-8 encoding is used when the ``--with-column`` mode is used. Thanks to Yann Leboulanger for the patch. * ``list_keys()`` now uses ``--fixed-list-mode``. Thanks to Werner Koch for the pointer. This release [2] has been signed with my code signing key: Vinay Sajip (CODE SIGNING KEY) Fingerprint: CA74 9061 914E AC13 8E66 EADB 9147 B477 339A 9B86 What Does It Do? ================ The gnupg module allows Python programs to make use of the functionality provided by the Gnu Privacy Guard (abbreviated GPG or GnuPG). Using this module, Python programs can encrypt and decrypt data, digitally sign documents and verify digital signatures, manage (generate, list and delete) encryption keys, using proven Public Key Infrastructure (PKI) encryption technology based on OpenPGP. This module is expected to be used with Python versions >= 2.4, as it makes use of the subprocess module which appeared in that version of Python. This module is a newer version derived from earlier work by Andrew Kuchling, Richard Jones and Steve Traugott. A test suite using unittest is included with the source distribution. Simple usage: >>> import gnupg >>> gpg = gnupg.GPG(gnupghome='/path/to/keyring/directory') >>> gpg.list_keys() [{ ... 'fingerprint': 'F819EE7705497D73E3CCEE65197D5DAC68F1AAB2', 'keyid': '197D5DAC68F1AAB2', 'length': '1024', 'type': 'pub', 'uids': ['', 'Gary Gross (A test user) ']}, { ... 'fingerprint': '37F24DD4B918CC264D4F31D60C5FEFA7A921FC4A', 'keyid': '0C5FEFA7A921FC4A', 'length': '1024', ... 'uids': ['', 'Danny Davis (A test user) ']}] >>> encrypted = gpg.encrypt("Hello, world!", ['0C5FEFA7A921FC4A']) >>> str(encrypted) '-----BEGIN PGP MESSAGE-----\nVersion: GnuPG v1.4.9 (GNU/Linux)\n \nhQIOA/6NHMDTXUwcEAf . -----END PGP MESSAGE-----\n' >>> decrypted = gpg.decrypt(str(encrypted), passphrase='secret') >>> str(decrypted) 'Hello, world!' >>> signed = gpg.sign("Goodbye, world!", passphrase='secret') >>> verified = gpg.verify(str(signed)) >>> print "Verified" if verified else "Not verified" 'Verified' As always, your feedback is most welcome (especially bug reports [3], patches and suggestions for improvement, or any other points via the mailing list/discussion group [4]). Enjoy! Cheers Vinay Sajip Red Dove Consultants Ltd. [1] https://bitbucket.org/vinay.sajip/python-gnupg [2] https://pypi.python.org/pypi/python-gnupg/0.4.0 [3] https://bitbucket.org/vinay.sajip/python-gnupg/issues [4] https://groups.google.com/forum/#!forum/python-gnupg From fabiofz at gmail.com Tue Jan 31 12:17:42 2017 From: fabiofz at gmail.com (Fabio Zadrozny) Date: Tue, 31 Jan 2017 15:17:42 -0200 Subject: PyDev 5.5.0 Released Message-ID: PyDev 5.5.0 Release Highlights ------------------------------- * **Important** PyDev now requires Java 8 and Eclipse 4.6 (Neon) onwards. * PyDev 5.2.0 is the last release supporting Eclipse 4.5 (Mars). * If you enjoy PyDev, you can help in keeping it supported through its Patreon crowdfunding: https://www.patreon.com/fabioz. * **Refactoring** * Fixed refactoring error when dealing with imports which have a continuation char inside the module name part. **#PyDev-712** * When extracting a method, decorators are properly considered for the new method position. **#PyDev-321** * **Code completion** * When accessing enums, 'value' and 'name' are properly found. **#PyDev-591** * Code completion improved on method chaining. **#PyDev-636** and **#PyDev-583** * It's now possible to choose whether when a code-completion which adds a local import should add the import to the beginning of the function or the line above where it was requested. * It may be configured in the preferences (Preferences > PyDev > Editor > Code Completion > Put local imports on top of method?). * Default was changed to add it to the top of the method. * **New actions** * **Ctrl+Shift+Alt+O** can be used to open the last hyperlink in the console that's currently open (it's now possible to jump directly to the error in some exception). **#PyDev-755** * **Ctrl+2,sw** switches the target and value in assign statements (may not work properly if more than one '=' is found in the line). * **Debugger** * Fixed error when hovering over variable when debugging. **#PyDev-580** * **Others** * Fixed issue in grammar parsing on nested async calls. **#PyDev-753** * Fixed issue grouping imports when an import has a continuation char inside the module part. **#PyDev 712** What is PyDev? --------------------------- PyDev is an open-source Python IDE on top of Eclipse for Python, Jython and IronPython development. It comes with goodies such as code completion, syntax highlighting, syntax analysis, code analysis, refactor, debug, interactive console, etc. Details on PyDev: http://pydev.org Details on its development: http://pydev.blogspot.com What is LiClipse? --------------------------- LiClipse is a PyDev standalone with goodies such as support for Multiple cursors, theming, TextMate bundles and a number of other languages such as Django Templates, Jinja2, Kivy Language, Mako Templates, Html, Javascript, etc. It's also a commercial counterpart which helps supporting the development of PyDev. Details on LiClipse: http://www.liclipse.com/ Cheers, -- Fabio Zadrozny ------------------------------------------------------ Software Developer LiClipse http://www.liclipse.com PyDev - Python Development Environment for Eclipse http://pydev.org http://pydev.blogspot.com PyVmMonitor - Python Profiler http://www.pyvmmonitor.com/