I would like to announce Datagram Transport Layer Security for
Python. From the top of the project README:
PyDTLS brings Datagram Transport Layer Security (DTLS - RFC 6347:
http://tools.ietf.org/html/rfc6347) to the Python environment. In a
nutshell, DTLS brings security (encryption, server authentication,
user authentication, and message authentication) to UDP datagram
payloads in a manner equivalent to what SSL/TLS does for TCP stream
DTLS is now very easy to use in Python. If you're familiar with the
ssl module in Python's standard library, you already know how. All it
takes is passing a datagram/UDP socket to the *wrap_socket* function
instead of a stream/TCP socket. Here's how one sets up the client side
of a connection:
from socket import socket, AF_INET, SOCK_DGRAM
from dtls import do_patch
sock = ssl.wrap_socket(socket(AF_INET, SOCK_DGRAM))
The project is hosted at https://github.com/rbit/pydtls, and licensed under
the Apache license 2.0. PyPI has packages. I can be reached
at code AT liquibits DOT com for questions, feedback, etc.
<P><A HREF="http://pypi.python.org/pypi/Dtls/0.1.0">Dtls 0.1.0</A> -
Datagram Transport Layer Security for Python. (07-Jan-13)
On the behalf of Spyder's development team
(http://code.google.com/p/spyderlib/people/list), I'm pleased to
announce that Spyder v2.1.13 has been released and is available for
Windows XP/Vista/7, GNU/Linux and MacOS X:
This is a pure maintenance release -- a lot of bugs were fixed since
v2.1.11 (v2.1.12 was released exclusively inside WinPython
Spyder is a free, open-source (MIT license) interactive development
environment for the Python language with advanced editing, interactive
testing, debugging and introspection features. Originally designed to
provide MATLAB-like features (integrated help, interactive console,
variable explorer with GUI-based editors for dictionaries, NumPy
arrays, ...), it is strongly oriented towards scientific computing and
Thanks to the `spyderlib` library, Spyder also provides powerful
ready-to-use widgets: embedded Python console (example:
http://packages.python.org/guiqwt/_images/sift3.png), NumPy array
editor (example: http://packages.python.org/guiqwt/_images/sift2.png),
dictionary editor, source code editor, etc.
Description of key features with tasty screenshots can be found at:
On Windows platforms, Spyder is also available as a stand-alone
executable (don't forget to disable UAC on Vista/7). This all-in-one
portable version is still experimental (for example, it does not embed
sphinx -- meaning no rich text mode for the object inspector) but it
should provide a working version of Spyder for Windows platforms
without having to install anything else (except Python 2.x itself, of
Don't forget to follow Spyder updates/news:
* on the project website: http://code.google.com/p/spyderlib/
* and on our official blog: http://spyder-ide.blogspot.com/
Last, but not least, we welcome any contribution that helps making
Spyder an efficient scientific development/computing environment. Join
us to help creating your favourite environment!
I've just uploaded pypiserver 1.0.1 to the python package index.
pypiserver is a minimal PyPI compatible server. It can be used to serve
a set of packages and eggs to easy_install or pip.
pypiserver is easy to install (i.e. just 'pip install pypiserver'). It
doesn't have any external dependencies.
http://pypi.python.org/pypi/pypiserver/ should contain enough
information to easily get you started running your own PyPI server in a
The code is available on github: https://github.com/schmir/pypiserver
Changes in version 1.0.1
- make 'pypi-server -Ux' work on windows
('module' object has no attribute 'spawnlp',
- use absolute paths in hrefs for root view
- add description of uploads to the documentation
- make the test suite work on python 3
- make pypi-server-standalone work with python 2.5
Happy new year! :)
New year, new release: Nanpy 0.7 is out with some changes:
- Now we use the official version of edam's Arduino makefile
- Added support to the CapacitiveSensor library
and map function
- Improvements on the communication speed and bugfixing
We also have a repository with some projects made using Nanpy:
https://github.com/nanpy/eggsamples ... if you have a project made
with Nanpy and it's open source please let us know!! :)
Enjoy Nanpy and discover its simplicity expecially using it with a
RaspberryPi.. in the last MagPi issue I explain how to accomplish
Remember that Nanpy is now an organization on Github! Join us and/or
donate if you like it!
WHAT IS NANPY
Nanpy is a pure Python library that allows you communicating with an
Arduino board connected via USB. Classes and methods used are really
similar to the Arduino framework's ones, but simpler and with some
additional features, so people who haven't worked with an Arduino can
be easily introduced to his world.. The main purpose of Nanpy is
making developers' life easier, giving them something simple and fast
to use to create prototypes and scripts interacting with Arduino,
saving time and making them concentrate on the problem.
There are a lot of projects able to do something similar, using Python
or other languages, but Nanpy can do more! Nanpy is easily extensible
and can theoretically use every library Arduino supports, allowing you
to create how many objects you want and without worrying about
deallocation. Also, you can use Nanpy in parallel and concurrence
programs. Nanpy is under heavy development but is growing fast and
just supports the main methods of OneWire, Lcd, Tone,
DallasTemperature, Stepper and Servo libraries. Just a word of
warning: Raspberry Pi may not provide enough power to drive an
Arduino, so you might need external power.
UNDER THE WOOD
With Nanpy you can write your Arduino programs using Python,
communicating via serial port without sending hard-to-remember codesor
limiting you to use only one object: when you create an object in
Python it will be automatically created into your Arduino at runtime..
For example if you write something like
tone = Tone(13)
lcd = Lcd([7, 8, 9, 10, 11, 12], [16, 2])
ds = DallasTemperature(5)
Nanpy creates the correct object into Arduino for you.. Also, you haven't to
take care of deallocation, Nanpy deallocates objects into Arduino as
soon as the correspondent Python objects get deleted. Look at the
examples to see how simple it is..
I tried running Nanpy on a Raspberry board and it works great!!(that's
the result from one of my friends' Twitter account
https://twitter.com/andreagrandi/status/251702684380434434 :) ). Also
you can use it in other devices suppoting Python and serial
communication, with Django, for creating prototypes
faster etc.. because you use Python and you don't have to flash the
firmware every time. Last but not least, firmware part of Nanpy is
Python-indipendent, so you can write another implementation of Nanpy
in any other language, for example Java, and see an Arduino controlled
via Android (ok, in this case we should use Android USB Host API,
writing our own driver, because Android doesn't provide anything to
access device files). We will work on this in the future :)
Do you like Nanpy? Contributions/suggestions/bug reporting/spreading
the project/beers/coffee are accepted :) if you want to donate a coffee
and be sure that we will work during the night, here's the link
Thanks for your attention!
Andrea Stagi (@4ndreaSt4gi) - Software Engineer
Job profile: http://linkedin.com/in/andreastagi
I'm pleased to announce sqlparse 0.1.5.
sqlparse is a non-validating SQL parser module.
This release improves Python 3 compatibility and has some minor bug fixes.
Changes since 0.1.5
sqlparse is now compatible with Python 3 without any patches. The
Python 3 version is generated during install by 2to3. You'll need
distribute to install sqlparse for Python 3.
* Fix parsing error with dollar-quoted procedure bodies (issue83).
* Documentation updates.
* Test suite now uses tox and py.test.
* py3k fixes (by vthriller).
* py3k fixes in setup.py (by Florian Bauer).
* setup.py now requires distribute (by Florian Bauer).
Best regards & a happy new year to everyone!
pydbgr is a somewhat large Python debugger modelled on the gdb command set. (Yes, I know this name is really horrible).
I am pleased (or is it relieved?) to release a version of pydbr that has a couple of features I have in other debuggers I've written, namely:
1. Terminal output is now syntax highlighted (via pygments). And other section or error like output uses terminal control too. To turn that off use "set highlight display" or the --no-highlight option when invoking the debugger.
2. Smart "eval". A plain eval will evaluate the source line of code that is about to be run. If you enter eval? Then the most common expression portion of the source line is evaluated. For example if the source line is
x = 1
Then eval will just run that. You don't have to cut and paste that source line. And eval? will evaluate just the RHS or 1.
There are a number of other features that the other debuggers have that I would eventually like to add:
* terminal debugger command completion
* better formatting using terminal control of help possibly using textile-like syntax
* syntax coloring disassembly code
* debugger macros as python code
but since this eval and syntax highlighting were so important, I thought I would rather have more smaller releases than one larger one.
Releases are available on pypi or the code repository http://code.google.com/p/pydbgr/