Thank you Bob for taking the time to clarify this for me. David
On Jul 24, 2011, at 1:47 PM, Bob Farrell <[email protected]> wrote: > Hi David, > > Yes, this is a "ten", not a "one". Obviously this is not correct if you take > this as a decimal fraction, but I can assure you that this is a common > convention for identifying versions and we are certainly not the only project > to follow this convention. > > As for the screenshots - bpython's filename completion (which is used > whenever you type a string literal) does path expansion (i.e. expands the > tilde `~` character to /home/currentuser) but os.listdir does not do this > (nor do any of the standard python file system functions). There is no > mistake here; python is erroring because there is no such file (you would > have to do `os.listdir(os.path.expanduser(...))`) and bpython is correctly > displaying the files found in the path-expanded location. > > I suppose we could change the screenshots to demonstrate this functionality > but using os.path.expanduser but I personally don't think this is really a > big deal. > > Hope this clears up your confusion, > > On 24 July 2011 15:40, David Dyck <[email protected]> wrote: > I saw > bpython-0.9.7.tar.gz 20-Jul-2010 14:48 81K > in the releases directory mentioned below, but > no bpython-1.0 > > > > Later - I looked at the dates of the files > bpython-0.1.5.tar.gz 05-Jun-2009 11:11 13K > bpython-0.10.tar.gz 23-Jul-2011 12:32 79K > bpython-0.2.0.tar.gz 05-Jun-2009 11:11 14K > > so I see there is a recent > bpython-0.10.tar.gz > > I guess I was confused that 0.10 was very different from 0.1 > I think this is a "ten", not another "point 1", right? > > Also, I have one question about the screenshots examples. > there's an example of path name expansion - in the first os.listdir > screenshot, that shows files in ~/irclogs/tweekers. Why did the next > screenshot then show an error that the directory did not exist? ( is it > because bpython is expanding the path name (with leading "`" differently than > python? ) > > Thanks, > David > > > > > On Sat, Jul 23, 2011 at 5:44 AM, Simon de Vlieger <[email protected]> wrote: > Hey hey hey, > > I am proud to announce release 0.10 of bpython. This is a bugfix > release. I've updated PyPI, the website and the IRC channel. The docs > website will follow suit shortly. You can fetch the new release from > our http://bpython-interpreter.org/releases/ website. > > We also took the opportunity to rework the branches and tags in both > our bpython and bpython-docs repositories to make parallel development > of the next version and bugfix releases easier to handle. > > The big change being the added i18n support by Michele, a big thanks to him! > > The changelog: > > v0.10 > ----- > As a highlight of the release, Michele Orrù added i18n support to bpython. > > Some issues have been resolved as well: > * Config files are now located according to the XDG Base Directory > Specification. The support for the old bpythonrc files has been > dropped and ~/.bpython.ini as config file location is no longer supported. > See issue #91. > * Fixed some issues with tuple unpacking in argspec. See issues #133 and #138. > * Fixed a crash with non-ascii filenames in import completion. See issue #139. > * Fixed a crash caused by inspect.findsource() raising an IndexError > which happens in some situations. See issue #94. > * Non-ascii input should work now under Python 3. > * Issue #165: C-a and C-e do the right thing now in urwid. > * The short command-line option "-c config" was dropped as it conflicts with > vanilla Python's "-c command" option. See issue #186. > > Regards, > > Simon de Vlieger > > -- > You received this message because you are subscribed to the Google Groups > "bpython" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/bpython?hl=en. > > > -- > You received this message because you are subscribed to the Google Groups > "bpython" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/bpython?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "bpython" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/bpython?hl=en. -- You received this message because you are subscribed to the Google Groups "bpython" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/bpython?hl=en.
