From benjamin at python.org Thu Sep 11 23:53:17 2014
From: benjamin at python.org (Benjamin Peterson)
Date: Thu, 11 Sep 2014 17:53:17 -0400
Subject: [Python-porting] six 1.8.0 released
Message-ID: <1410472397.2792960.166501445.7E2B2549@webmail.messagingengine.com>
I'm pleased to announce the latest release of six, a Python 2/3
compatibility library. Many more "six.moves" mappings were added, and a
few bugs were fixed.
Download six from PyPI: https://pypi.python.org/pypi/six
Report bugs: https://bitbucket.org/gutworth/six
Here is the full changelog for this release:
- Issue #90: Add six.moves.shlex_quote.
- Issue #59: Add six.moves.intern.
- Add six.urllib.parse.uses_(fragment|netloc|params|query|relative).
- Issue #88: Fix add_metaclass when the class has __slots__ containing
"__weakref__" or "__dict__".
- Issue #89: Make six use absolute imports.
- Issue #85: Always accept *updated* and *assigned* arguments for
wraps().
- Issue #86: In reraise(), instantiate the exception if the second
argument is
None.
- Pull request #45: Add six.moves.email_mime_nonmultipart.
- Issue #81: Add six.urllib.request.splittag mapping.
- Issue #80: Add six.urllib.request.splituser mapping.
From luiz.r.silva at exxonmobil.com Tue Sep 2 20:48:48 2014
From: luiz.r.silva at exxonmobil.com (Silva, Luiz R)
Date: Tue, 2 Sep 2014 15:48:48 -0300
Subject: [Python-porting] Siz 1.7.3
Message-ID: <E4471604B2CF51429A4D1C790010E3D0418EBAEC16@CTCEXM02.SA.XOM.COM>
Hi,
Can you help me to identify what is the license agreement for Six? It's a GNU?
"Six is a Python 2 and 3 compatibility library. It provides utility functions for smoothing over the differences between the Python versions with the goal of writing Python code that is compatible on both Python versions. See the documentation for more information on what is provided"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20140902/0689b22e/attachment.html>
From regebro at gmail.com Fri Sep 12 15:03:01 2014
From: regebro at gmail.com (Lennart Regebro)
Date: Fri, 12 Sep 2014 15:03:01 +0200
Subject: [Python-porting] Siz 1.7.3
In-Reply-To: <E4471604B2CF51429A4D1C790010E3D0418EBAEC16@CTCEXM02.SA.XOM.COM>
References: <E4471604B2CF51429A4D1C790010E3D0418EBAEC16@CTCEXM02.SA.XOM.COM>
Message-ID: <CAL0kPAUY+_xHewq3VVm1JE=CNPUMwHFi6edoDf=_iAmFEGRtSQ@mail.gmail.com>
>From https://pypi.python.org/pypi/six
- *License:* MIT
It also has a license file in the tgz file.
On Tue, Sep 2, 2014 at 8:48 PM, Silva, Luiz R <luiz.r.silva at exxonmobil.com>
wrote:
> Hi,
>
>
>
> Can you help me to identify what is the license agreement for Six? It?s a
> GNU?
>
>
>
>
>
> ?Six is a Python 2 and 3 compatibility library. It provides utility
> functions for smoothing over the differences between the Python versions
> with the goal of writing Python code that is compatible on both Python
> versions. See the documentation for more information on what is provided?
>
> _______________________________________________
> Python-porting mailing list
> Python-porting at python.org
> https://mail.python.org/mailman/listinfo/python-porting
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20140912/7b805fad/attachment.html>
From mrichardson3 at gmail.com Fri Sep 19 22:38:01 2014
From: mrichardson3 at gmail.com (Mark Richardson)
Date: Fri, 19 Sep 2014 16:38:01 -0400
Subject: [Python-porting] Possible bug: Using futurize,
code blows up around line 271 in main.py
Message-ID: <541C9429.8060901@gmail.com>
Greetings all,
It's my first post, so if I'm breaking protocol, please forgive. Tried
running futurize on
some of my old python2 code and the futurizer blew up around line 271
with error:
NameError: name 'logger' is not defined
The original line starts with
logger.info('Output ...
and I think it should be
logging.info('Output ...
First off, I'm not sure if this is what the author intended and secondly,
if it is what the author intended, what is the method that I go about to see
that the bug gets corrected? I'm perfectly fine, with fixing my own copy
to get it to run, but it seems like I should generate a resolution to
the source
code so that the next guy/gal doesn't have to go down the same rabbit
hole. If there's a link to a rtfm page for these type of issues, I'm
more than
happy to read it and reapply my issue again.
Thanks,
Mark R.
From mrichardson3 at gmail.com Fri Sep 19 23:47:33 2014
From: mrichardson3 at gmail.com (Mark Richardson)
Date: Fri, 19 Sep 2014 17:47:33 -0400
Subject: [Python-porting] Possible bug on line 28 of file:
https://github.com/PythonCharmers/python-future/blob/master/libfuturize/main.py
Message-ID: <541CA475.4000204@gmail.com>
Dear Gentlepeople,
In file
https://github.com/PythonCharmers/python-future/blob/master/libfuturize/main.py
on line 228 the source code is:
extra_fixes.add(prefix+'fix_add_all_future_builtins')
The program fails with the error:
Import Error: No module named libfuturize.fixes.fix_add_all_future_builtins
I checked the "fixes" subdirectory and do not readily find any file that
looks like it could be a typo or what not. I'll comment the line out and
carry
on, but just in case it's important, I thought I'd shine a light on it.
Thanks so much,
Mark R.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20140919/7d77b871/attachment.html>
From guido at python.org Mon Sep 22 18:25:15 2014
From: guido at python.org (Guido van Rossum)
Date: Mon, 22 Sep 2014 09:25:15 -0700
Subject: [Python-porting] Possible bug: Using futurize,
code blows up around line 271 in main.py
In-Reply-To: <541C9429.8060901@gmail.com>
References: <541C9429.8060901@gmail.com>
Message-ID: <CAP7+vJL+k7Aw44dtrb-4u9+M-e3TuzkL0uq5HfCFLhGkNvUJQg@mail.gmail.com>
Hi Mark,
You probably want to file a bug report with the futurizer's project. Try
the issue tracker there (if I understand the project you're using):
https://github.com/PythonCharmers/python-future/issues
Thanks for reporting!
On Fri, Sep 19, 2014 at 1:38 PM, Mark Richardson <mrichardson3 at gmail.com>
wrote:
> Greetings all,
>
> It's my first post, so if I'm breaking protocol, please forgive. Tried
> running futurize on
> some of my old python2 code and the futurizer blew up around line 271 with
> error:
>
> NameError: name 'logger' is not defined
>
> The original line starts with
>
> logger.info('Output ...
>
> and I think it should be
>
> logging.info('Output ...
>
> First off, I'm not sure if this is what the author intended and secondly,
> if it is what the author intended, what is the method that I go about to
> see
> that the bug gets corrected? I'm perfectly fine, with fixing my own copy
> to get it to run, but it seems like I should generate a resolution to the
> source
> code so that the next guy/gal doesn't have to go down the same rabbit
> hole. If there's a link to a rtfm page for these type of issues, I'm more
> than
> happy to read it and reapply my issue again.
>
>
> Thanks,
> Mark R.
>
>
> _______________________________________________
> Python-porting mailing list
> Python-porting at python.org
> https://mail.python.org/mailman/listinfo/python-porting
>
--
--Guido van Rossum (python.org/~guido)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20140922/535b0b04/attachment.html>
From ed at pythoncharmers.com Tue Sep 23 06:50:42 2014
From: ed at pythoncharmers.com (Ed Schofield)
Date: Tue, 23 Sep 2014 14:50:42 +1000
Subject: [Python-porting] Possible bug: Using futurize,
code blows up around line 271 in main.py
In-Reply-To: <541C9429.8060901@gmail.com>
References: <541C9429.8060901@gmail.com>
Message-ID: <A9CB4388-1598-4141-9E83-03004BBB873B@pythoncharmers.com>
Hi Mark,
Yes, thanks for your bug reports!
I have filed them as issues #101 and #102 at the URL Guido posted. They should now be fixed in v0.13.1 on PyPI.
Please let me know if you have any other questions. Good luck with your porting!
Cheers,
Ed
On 20 Sep 2014, at 6:38 am, Mark Richardson <mrichardson3 at gmail.com> wrote:
> Greetings all,
>
> It's my first post, so if I'm breaking protocol, please forgive. Tried running futurize on
> some of my old python2 code and the futurizer blew up around line 271 with error:
>
> NameError: name 'logger' is not defined
>
> The original line starts with
>
> logger.info('Output ...
>
> and I think it should be
>
> logging.info('Output ...
>
> First off, I'm not sure if this is what the author intended and secondly,
> if it is what the author intended, what is the method that I go about to see
> that the bug gets corrected? I'm perfectly fine, with fixing my own copy
> to get it to run, but it seems like I should generate a resolution to the source
> code so that the next guy/gal doesn't have to go down the same rabbit
> hole. If there's a link to a rtfm page for these type of issues, I'm more than
> happy to read it and reapply my issue again.
>
>
> Thanks,
> Mark R.
>
>
> _______________________________________________
> Python-porting mailing list
> Python-porting at python.org
> https://mail.python.org/mailman/listinfo/python-porting
--
Dr. Edward Schofield
Python Charmers
http://pythoncharmers.com
From ashwath.utd at gmail.com Tue Sep 23 10:21:49 2014
From: ashwath.utd at gmail.com (Ashwath Kumar K)
Date: Tue, 23 Sep 2014 08:21:49 -0000
Subject: [Python-porting] Unsubscribe
Message-ID: <CAPH+wqBvUTboYtvgtdEptzOONpB9rxSKC-6fdd6M6wYDa+ZSaQ@mail.gmail.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-porting/attachments/20140923/c0d2b847/attachment-0001.html>