Mailman 3 January 2017 - Python-announce-list

Announcement: TLSv1.2 will become mandatory in the future for Python.org Sites
by Donald Stufft 10 Jan '17

10 Jan '17

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.

1 0

ANN: Bokeh 0.12.4 Released
by Bryan Van de Ven 09 Jan '17

09 Jan '17

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(a)continuum.io or the Gitter Chat room: https://gitter.im/bokeh/bokeh Thanks, Bryan Van de Ven

1 0

Announcing txAWS 0.2.3.1
by Jean-Paul Calderone 09 Jan '17

09 Jan '17

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, <https://github.com/twisted/txaws >. Special thanks to Least Authority Enterprises (<https://leastauthority.com/>) for sponsoring the work to find and fix this issue and to publish this new release. Jean-Paul

1 0

Nikola v7.8.2 is out!
by Chris Warrick 08 Jan '17

08 Jan '17

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)

1 0

[ANN] pyspread 1.1
by Martin Manns 08 Jan '17

08 Jan '17

============== 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 <Ctrl>+<Alt>+C and <Ctrl>+<Alt>+V . Copying formats has been decoupled from content in order to avoid unwanted side effects that can be experienced in current Office suites. * <F6> 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

1 0

cx_Freeze 5.0.1
by Anthony Tuininga 07 Jan '17

07 Jan '17

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

1 0

[ANN] Pythran O.8.0 is out
by serge guelton 06 Jan '17

06 Jan '17

(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!

1 0

ANN: Python Events Calendar - Please submit your 2017 events
by M.-A. Lemburg 06 Jan '17

06 Jan '17

[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/

1 0

<Programming> 2017: Call for workshop, symposium & poster submissions
by Tim Molderez 06 Jan '17

06 Jan '17

----------------------------------------------------------------------- <Programming> 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 <Programming> 2017 conference (and more to come!): - ELS 2017 - 10th European Lisp Symposium - Modularity 2017 Invited talks - International Symposium on Modularity - ACM Student Research Competition / <Programming> 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 / <Programming> 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.

1 0

Vulture 0.12
by Jendrik Seipp 05 Jan '17

05 Jan '17

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

1 0