Mailman 3 October 2014 - Python-announce-list

EuroPython Workgroups: Call for Volunteers
by M.-A. Lemburg Oct. 11, 2014

Oct. 11, 2014

(This post is also available for online reading at: http://www.europython-society.org/post/99718376575/europython-workgroups-ca…) Dear EuroPython community, the EuroPython Society is happy to announce a new organizational concept that we'd like to put in place for the next EuroPython conferences: the EuroPython Workgroups. Motivation ---------- In the past, the EPS granted permission to use the brand to local organizers based on a set of requirements, and the local organizing team then had to run the event in collaboration with the EPS. Most of the work was centered around the local team. This model no longer scales and doesn’t encourage the community to take part in the organization process. The workload and the financial risks of running such a big conference for the local teams is very high. Proposed New Structure (Workgroups) ----------------------------------- The biggest change is the introduction of permanent workgroups integrated with EPS and its activities. This change is designed to address the issues mentioned above in a way which allows our community to get more involved, while at the same time reducing the risk and work load on individual teams. Workgroups will be coordinated by the EuroPython Society board based on the community feedback and proposals, from their definition and creation to their implementation. The key workgroups we have identified so far are: * Conference Administration (contracts, venue contact, ticket support, satellite conferences, legal support, insurance, licensing) * Finance (budget, controlling, accounting, billing, invoicing, taxes, payment system administration, Treasurer needs be part of this WG) * Sponsors (sponsor contacts, sponsor logistics, room/booth assignment, recruiting session, jobs fair, exhibit hall, startup row) * Communications (press, community relations, diversity/outreach/CoC, CoC contact, announcements, social media, attendee tools, volunteer coordination, mailing lists) * Support (helpdesk, attendee support contact, visa help, travel management, chat support for attendees) * Financial Aid (setup, grant selection, aid organisation) * Marketing/Design (brochures, advertisements, banners, flyers, travel guide, t-shirts, lanyards, badges, panels, logo) * Program (talk selection, scheduling, session chairs, sprint/openspace/keynote/lightning talks/poster session organization, Young Coders session, Python for Teachers) * Web (web site support, ticket system, administration, backups, payment system integration, hosting, chat support for attendees) * Media (video recording, live streaming, live translations, uploads to YouTube and archive.org) * On-site Team (on-site support, local contact, help with venue selection, help with catering selection, partner program, social events, buddy program, internet access, venue contact, catering contact, on-site logistics) All of these workgroups, except for the On-site Team, will remain active when changing location. We expect to keep institutional knowledge within the organization and make transitions to new locations easier by using this approach. The EuroPython Society collects and reviews the applications to each workgroup. The EPS board will then vote on the chair and a set of permanent workgroup members with (workgroup internal) voting rights and then have the workgroup chair appoint additional (non-voting) members as necessary. Workgroups will be confirmed/reestablished by board vote every year, this allows non-voting members to become voting members in the following year. Workgroups and board will update, coordinate and plan activities on a regular basis. While every workgroup will be responsible for its own coordination and establish a workflow that best fits its needs, we expect all workgroups to integrate and interact with other workgroups to create a productive work environment. To simplify and speed up the workgroup setup, we will create a set of workgroup guidelines which aim at collecting the institutional knowledge gathered over the years. We will put these guidelines up for comment in the coming weeks. Call for Volunteers ------------------- Please help us build EuroPython and keep making it better and better every year. If you want to help, please apply for one or more workgroups which you feel match your interests and experience. If you'd like to help, but don't have enough experience, yet are willing to learn, please apply as well. To apply please send an email to board(a)europython.eu with your details, the motivation for applying (basically why and how you think you could help) and the workgroup(s) you'd like to apply for. Just to clarify: We will issue a separate Call for Participation (CFP) for the On-site Team, so you don't need to apply for this workgroup before we have selected an On-site Team. Thank you, -- EuroPython Society

1 0

About publishing a library
by Schnupsel Lee Oct. 10, 2014

Oct. 10, 2014

Hi there I have recently made a program for my class project. The program is able to convert the math equations that user type in directly in the raw_input as a string into math equations and do calculations. I found the program convenient to use so I am wondering if I can make it a public library for the other people to use. However, I dont know much about the procedures? Hao Lee

1 0

Karlsruhe (Germany) Python User Group, October 17th 2014, 7pm
by Jürgen A. Erhard Oct. 10, 2014

Oct. 10, 2014

The Karlsruhe Python User Group (KaPy) meets again. Friday, 2014-10-17 (October 17th) at 19:00 (7pm) in the rooms of Entropia eV (the local affiliate of the CCC). See http://entropia.de/wiki/Anfahrt on how to get there. For your calendars: meetings are held monthly, on the 3rd Friday. There's also a mailing list at https://lists.bl0rg.net/cgi-bin/mailman/listinfo/kapy.

1 0

Sphinx 1.3 beta 1 released
by Takayuki Shimizukawa Oct. 9, 2014

Oct. 9, 2014

Hi all, I'm very happy to announce the release of Sphinx 1.3, beta 1, available on the Python package index at <http://pypi.python.org/pypi/Sphinx/1.3b1>. Please test and report bugs to <http://dev.sphinx-doc.org/sphinx/issues>. This is the first testing release for Sphinx 1.3, a new feature release with lots of improvements and new features. - Add support for Python 3.4 - Add support for docutils 0.12 - Drop support for docutils versions up to 0.9. - Drop support for Python 2.5, 3.1 and 3.2. - Add 'sphinx.ext.napoleon' extension for NumPy and Google style docstring support. - Add support for parallel reading (parsing) of source files (optional). - Add the 'any' role that can be used to find a cross-reference of *any* type in *any* domain. - Add various options to sphinx-quickstart. Quiet mode option '--quiet' will skip wizard mode. - Add numfig feature: assign numbers to figures, tables and code-blocks. - Add 'caption' parameter to 'code-block' and 'literalinclude'. - Add stemming support for 14 languages. - Add new theme: bizstyle. For the full changelog, go to: https://bitbucket.org/birkenfeld/sphinx/src/701b48f97/CHANGES 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/ Enjoy! -- Takayuki SHIMIZUKAWA http://about.me/shimizukawa

1 0

ANN: python-ldap 2.4.18
by Michael Ströder Oct. 9, 2014

Oct. 9, 2014

Find a new release of python-ldap: http://pypi.python.org/pypi/python-ldap/2.4.18 python-ldap provides an object-oriented API to access LDAP directory servers from Python programs. It mainly wraps the OpenLDAP 2.x libs for that purpose. Additionally it contains modules for other LDAP-related stuff (e.g. processing LDIF, LDAP URLs and LDAPv3 schema). Project's web site: http://www.python-ldap.org/ Ciao, Michael. ---------------------------------------------------------------- Released 2.4.18 2014-10-09 Changes since 2.4.17: Lib/ * Fixed raising exception in LDAPObject.read_s() when reading an entry returns empty search result

1 0

[RELEASE] Python 3.4.2 is now available
by Larry Hastings Oct. 8, 2014

Oct. 8, 2014

On behalf of the Python development community and the Python 3.4 release team, I'm pleased to announce the availability of Python 3.4.2. Python 3.4.2 has many bugfixes and other small improvements over 3.4.1. One new feature for Mac OS X users: the OS X installers are now distributed as signed installer package files compatible with the OS X Gatekeeper security feature. You can download it here: https://www.python.org/download/releases/3.4.2 May the road rise up to meet you, //arry/

1 0

ANN: rom 0.29.0 - Redis object mapper for Python
by Josiah Carlson Oct. 6, 2014

Oct. 6, 2014

Hey everyone, The "rom" package is a Redis object mapper for Python. It sports an interface similar to Django's ORM, SQLAlchemy with the declarative base, or Appengine's datastore. The changelog for recent releases can be seen below my signature. You can find the package at: https://www.github.com/josiahcarlson/rom https://pypi.python.org/pypi/rom And docs can be found at: http://pythonhosted.org/rom/ Please CC me on any replies if you have any questions or comments. Thank you, - Josiah #---------------------------------- 0.29.0 ----------------------------------- [added] Query result iterator: query.iter_result(timeout, pagesize) that automatically wraps query.cached_result(timeout) for convenient iteration over all entities in the query. Added at the request of Github user https://github.com/JamesHutchison . [added] On delete for OneToMany columns now support 'cascade' for recursively deleting all referencing entities. All on delete behavior is checked before deleting (a restrict in an entity after 100 levels of 'cascade' will prevent all deletions). Requested by https://github.com/JamesHutchison and closes issue #39. [added] OneToMany columns can now include a reference to the foreign model's ManyToOne column name that references *this* OneToMany. Useful for cases where models have multiple OneToMany or ManyToOne columns referencing the same models. Closes issue #23. [fixes] Index clearing with util.clean_old_index() [changed] Index clearing with util.clean_old_index() will also clean out index data for entities directly deleted or expired in Redis. Closes issue #40. #---------------------------------- 0.28.0 ----------------------------------- [added] Composite unique constraints like SQLAlchemy's UniqueConstraint() and Django's unique_together, spelled and used like Django's unique_together. See http://pythonhosted.org//rom/rom.html#rom.Model for details. [fixed] Deleting entities will no longer leave extra index data around (regardless of whether the entitiy had any indexes defined). [added] Convenience function for cleaning out old index data from deleted entities. See and read the help on util.clean_old_index() . [added] Convenience function util.show_progress() to show the progress of util.refresh_indices() and util.clean_old_index() . See and read the help on util.show_progress() for usage. [fixed] Tests to no longer leave testing data in db 15, and running tests again should clean out the testing data. [fixed] Incorrect documentation about the String column type. #---------------------------------- 0.27.0 ----------------------------------- [changed] Added auto-tagging support for release versions pushed to PyPI. [added] Foreign key references defined with a OneToMany and ManyToOne relationship will now have the "one" side of the relationship deletion optionally restrict. Thanks to https://github.com/pconerly for the initial request and patch. [added] Additional warnings and tests for future on_delete behavior choices. [fixed] Re-save issue for datetime objects, as well as any future re-save issues (like what happened with json columns in rom 0.15). Thanks to https://github.com/iamkhush for the bug report and example testcase that lead to the solution.

1 0

[RELEASED] Python 3.2.6rc1, Python 3.3.6rc1
by Georg Brandl Oct. 4, 2014

Oct. 4, 2014

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On behalf of the Python development team, I'm happy to announce the release of Python 3.2.6rc1 and 3.3.6rc1. Both are release candidates for security-fix releases, which are provide source-only on python.org. The list of security-related issues fixed in the releases is given in the changelogs: https://hg.python.org/cpython/raw-file/v3.2.6rc1/Misc/NEWS https://hg.python.org/cpython/raw-file/v3.3.6rc1/Misc/NEWS To download the pre-releases visit one of: https://www.python.org/downloads/release/python-326rc1/ https://www.python.org/downloads/release/python-336rc1/ These are pre-releases, please report any bugs to http://bugs.python.org/ The final releases are scheduled one week from now. Enjoy! - -- Georg Brandl, Release Manager georg at python.org (on behalf of the entire python-dev team and contributors) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlQv9GsACgkQN9GcIYhpnLC93gCfVm74lhOysPYCO0fy9/l5LUfJ bUYAn2u1EygfsPw2oa4CSoj5t0TYUJq7 =HnOK -----END PGP SIGNATURE-----

1 0

ANN: dh-virtualenv 0.8 released
by Jyrki Pulliainen Oct. 2, 2014

Oct. 2, 2014

Hello, I'm pleased to announce that we at Spotify have released dh-virtualenv 0.8! Dh-virtualenv is a packaging tool that makes it possible to package virtualenvs inside Debian packages. dh-virtualenv works by registering itself as a part of debhelper sequence, so pretty much any pre-existing Debian build system you have should be compatible with it. Changelog since version 0.8: - Support for running triggers upon host interpreter update. This new feature makes it possible to upgrade the host Python interpreter and avoid breakage of all the virtualenvs installed with dh-virtualenv. - Support for the built-in (Python 3.3+) venv module - Ability to pass custom pip arguments to be passed with --extra-pip-args flag I would like to thank all the contributors and especially Jürgen Hermann for implementing the Python interpreter trigger! For more information, see documentation here: http://dh-virtualenv.readthedocs.org/en/0.8/index.html And source code here: https://github.com/spotify/dh-virtualenv/tree/0.8 Cheers, Jyrki Pulliainen Content Engineer @ Spotify

1 0

[ANN] Nanpy 0.9.2
by Andrea Stagi Oct. 2, 2014

Oct. 2, 2014

Hi all, I'm glad to announce you Nanpy 0.9.2 release, with little fixes on DallasTemperature module! https://pypi.python.org/pypi/nanpy/0.9.2 We need contributors! Nanpy needs a lot of work to be a great tool. You can contribute with code (bugfixing, improvements, creating support for a new library not included in Nanpy yet, writing examples and more), writing documentation, reporting bugs, creating packages or simply spreading Nanpy through the web if you like it :) Our organization works on Github at https://github.com/nanpy Do you want to support us with a coffee? We need it to code all night long! if you like this project and you want to support it with some cents, please donate :) https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=TDTPP5… If you have any doubt or problem, please contact me at stagi dot andrea at gmail dot com What you can do with Nanpy ------------------------------------ The main purpose of Nanpy is making programmers' life easier, giving them something to create prototypes faster and use Arduino in a simpler way, thanks to a simple and powerful language like Python. Also Nanpy can run on RaspberryPi (tested with Raspbian http://www.raspbian.org/) so you can use it for communicating with Arduino and create awesome projects like Chickenfoot (https://www.youtube.com/watch?v=g8FywaVDCes) :) Let's start with a classic example, turn on a led placed in the 13th pin.. from nanpy import (ArduinoApi, SerialManager) connection = SerialManager() a = ArduinoApi(connection=connection) a.pinMode(13, a.OUTPUT) a.digitalWrite(13, a.HIGH) NOTE: you can also use the old serial_manager global object Nanpy autodetects the serial port for you, anyway you can specify another serial port manually: from nanpy import SerialManager connection = SerialManager(device='/dev/ttyACM1') There are a lot of projects able to do that. Nanpy can do more! Nanpy is easily extensible and can theoretically use every library, allowing you to create how many objects you want. We started supporting OneWire, Lcd, Stepper and Servo library and they're still incomplete. Let's try to connect our 16x2 lcd screen on pins 7, 8, 9, 10, 11, 12 and print something! from nanpy import SerialManager, Lcd connection = SerialManager() lcd = Lcd([7, 8, 9, 10, 11, 12], [16, 2], connection=connection) lcd.printString("Hello World!") really straightforward now, isn't it? :) How to build and install ------------------------------ You need to build the firmware for your Arduino first, just clone the firmware repository at https://github.com/nanpy/firmware and follow the README to configure, build and upload it. To install Nanpy Python library just type (as root): python setup.py install -- Andrea Stagi (@4stagi) - Software Engineer @ Atooma Inc. Job profile: http://linkedin.com/in/andreastagi Website: http://4spills.blogspot.it/ Github: http://github.com/astagi

1 0