[ANN] MicroPython 1.6

Hello, MicroPython is a lean and efficient Python implementation for microcontrollers, embedded, and mobile systems (which also runs just as fine on desktops, servers, and clouds). https://github.com/micropython/micropython https://github.com/micropython/micropython/releases/tag/v1.6 There're fo

Re: [ANN] MicroPython 1.5

Hello, On Sun, 8 Nov 2015 12:08:20 -0700 paul.hermeneu...@gmail.com wrote: > What is the possibility that MicroPython could be another build from > the base python.org sources? Python already gets built for a variety > of architectures. Could a MicroPython be another one? In that way, it > would

Re: [ANN] MicroPython 1.5

Hello, On Sun, 08 Nov 2015 10:28:24 -0800 Paul Rubin wrote: > Paul Sokolovsky writes: > > Recent 1.5 release is an important milestone for the project, major > > changes including: > > Thanks for posting this. We don't hear enough about MicroPython on > this

[ANN] MicroPython 1.5

Hello, MicroPython is a lean and efficient Python implementation for microcontrollers, embedded, and mobile systems (which also runs just as fine on desktops of course). https://github.com/micropython/micropython Recent 1.5 release is an important milestone for the project, major changes includi

MicroPython 1.3.7 released

Hello, MicroPython is a Python3 language implementation which scales down to run on microcontrollers with tens of Ks of RAM and few hundreds of Ks of code size. Besides microcontrollers, it's also useful for small embedded Linux systems, where storage space is limited, for embedding as a scripting

Re: PEP8 and 4 spaces

Hello, On Fri, 4 Jul 2014 03:38:27 +1000 Chris Angelico wrote: > On Fri, Jul 4, 2014 at 3:31 AM, Tobiah wrote: > > Coworker takes PEP8 as gospel and uses 4 spaces > > to indent. I prefer tabs. Boss want's us to > > unify. > > 1) PEP 8 is meant to be guidelines, *not* a set of hard-and-fast >

Re: install software via Python script

Hello, On Wed, 2 Jul 2014 18:01:45 -0400 "Moshe Avraham" wrote: > HI Guys, > > I need to install variety of software (Oracle, SqlServer, upgrade JAVA > version, WAS, WMB, Tomcat, etc.) on both WINDOWS and UNIX/LINUX. > > These are usual daily operation of large IT departments. > > So instead

Re: What's the "right" way to abandon an open source package?

Hello, On 01 Jul 2014 18:40:23 GMT Steven D'Aprano wrote: > On Tue, 01 Jul 2014 20:59:48 +0300, Paul Sokolovsky wrote: > > > Put it on github > > > http://nedbatchelder.com/blog/201405/github_monoculture.html Everyone who (re)posts stuff like that should have

Re: What's the "right" way to abandon an open source package?

Hello, On Tue, 1 Jul 2014 12:30:44 -0500 Skip Montanaro wrote: > This is only Python-related because the package in question (lockfile > at PyPI) is written in Python and hosted (at least in part) on PyPI. I > have not had any interest in maintaining this package for a few years. > I wrote it mo

Re: What can Nuitka do?

Hello, On Fri, 27 Jun 2014 16:25:02 -0700 (PDT) CM wrote: > (Trying again, simpler and cleaner post) > > Can I use Nuitka to transform a wxPython > GUI application in Python that uses several > 3rd party modules into a small and faster > compiled-to-C executable? Yes, you can. So, please try

Re: Asymmetry in globals __getitem__/__setitem__

Hello, On Fri, 13 Jun 2014 12:53:54 +0200 Peter Otten <__pete...@web.de> wrote: [] > > exec(fun.__code__, {}, Namespace()) > > > > > > Neither __getitem__ nor __setitem__ seem to be called on the local > > variables. > > Accessing fun.__code__ is clever, but unfortunately the compiler > produ

Re: None in string => TypeError?

Hello, On Mon, 9 Jun 2014 08:34:42 -0700 (PDT) Roy Smith wrote: > We noticed recently that: > > >>> None in 'foo' > > raises (at least in Python 2.7) > > TypeError: 'in ' requires string as left operand, not NoneType > > This is surprising. The description of the 'in' operatator is, 'True >

Re: Uniform Function Call Syntax (UFCS)

Hello, On Sun, 08 Jun 2014 18:56:47 +0300 Marko Rauhamaa wrote: > Paul Sokolovsky : > > > Python already has that - like, len(x) calls x.__len__() if it's > > defined > > In fact, what's the point of having the duality? > >len(x) <==

Re: Uniform Function Call Syntax (UFCS)

Hello, On Sun, 8 Jun 2014 01:26:04 -0700 (PDT) jongiddy wrote: > On Sunday, 8 June 2014 02:27:42 UTC+1, Gregory Ewing wrote: > > > > Also it doesn't sit well with Python's "one obvious > > way to do it" guideline, because it means there are > > *two* equally obvious ways to call a function. >

Re: Uniform Function Call Syntax (UFCS)

Hello, On Sun, 8 Jun 2014 01:15:43 -0700 (PDT) jongiddy wrote: > Thanks for the extensive feedback. Here's my thoughts on how to > address these issues. > > On Saturday, 7 June 2014 20:20:48 UTC+1, Ian wrote: > > > > It's a nice feature in a statically typed language, but I'm not sure > > ho

Re: Micro Python -- a lean and efficient implementation of Python 3

Hello, On Wed, 4 Jun 2014 03:08:57 +1000 Chris Angelico wrote: [] > With that encouragement, I just cloned your repo and built it on amd64 > Debian Wheezy. Works just fine! Except... I've just found one fairly > major problem with your support of Python 3.x syntax. Your str type is > documented

Re: Micro Python -- a lean and efficient implementation of Python 3

Hello, On Tue, 3 Jun 2014 23:11:46 +1000 Chris Angelico wrote: > On Tue, Jun 3, 2014 at 10:27 PM, Damien George > wrote: > > - Supports almost full Python 3 syntax, including yield (compiles > > 99.99% of the Python 3 standard library). > > - It supports a growing subset of Python 3 types and o

Re: Benefits of asyncio

Hello, On Mon, 02 Jun 2014 21:51:35 -0400 Terry Reedy wrote: > To all the great responders. If anyone thinks the async intro is > inadequate and has a paragraph to contribute, open a tracker issue. Not sure about intro (where's that?), but docs (https://docs.python.org/3/library/asyncio.html)