search for: py3k

Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- com32/cmenu/menugen.py | 56 +++++++++++++++++++++++++------------------------- 1 file changed, 28 insertions(+), 28 deletions(-) diff --git a/com32/cmenu/menugen.py b/com32/cmenu/menugen.py index 70ec1f8..da64d93 100644 --- a/com32/cmenu/menugen.py +++ b/com32/cmenu/menugen.py @@ -72,9 +72,9 @@ class Menusystem:

...http://bb.pgr.jp/builders/clang-i686-cygwin-RA-centos6/builds/12836/steps/configure/logs/stdio >> http://lab.llvm.org:8011/builders/llvm-s390x-linux1/builds/12002/steps/configure/logs/stdio >> >> Should we just upgrade those bots or reduce the requirement to 2.6? > > 2.6 + py3k is a generally good combination for typical code and is easy to maintain. It is not possible to be both 2.5 and py3k compatible without huge hurdles. > Well, I am no Python expert either. I went with 2.7 because it was suggested and 4 years old software sounded old enough. If there are no ob...

...ing older versions is declining, the number of people running python3 will only increase. I believe that 2.6 was the first version that had the __future__ import print_function available, which means that python 2.4 and 2.5 would not be able to use print statements if they are to interoperate with py3k. There is also __cmp__() which has been removed in python3 and I saw in a couple places. The bottom line is that basically every guide to porting/interoperating with python3 starts with "step 1: use python 2.6 at least, ideally 2.7". Given the need to interoperate with py3k, the need to...

So far two bots have complained about 2.7 (but have 2.6): http://bb.pgr.jp/builders/clang-i686-cygwin-RA-centos6/builds/12836/steps/configure/logs/stdio http://lab.llvm.org:8011/builders/llvm-s390x-linux1/builds/12002/steps/configure/logs/stdio Should we just upgrade those bots or reduce the requirement to 2.6? On 12 December 2014 at 06:41, Dan Liew <dan at su-root.co.uk> wrote: > +1

On 12/04/2012 12:28 AM, Sean Silva wrote: > On Mon, Dec 3, 2012 at 6:56 AM, Tobias Grosser<tobias at grosser.es> wrote: >> The gcc compile farm currently only has python 2.4 and 2.5. I know Duncan is >> using it quiet extensively, especially all dragonegg buildbots run on it. >> >> I very much agree we should ensure our python scripts are valid python 2.7 >>

On Wed, Aug 14, 2013 at 1:15 PM, Tim Northover <t.p.northover at gmail.com>wrote: > > If anyone is interested in this support, I'd appreciate it if you changed > > your setup to use Python3 for running the tests and let me know (or file > > bugs) for any issues you find. > Great work, Daniel. All LLVM tests pass for me on trunk when running with Python 3.4 alpha.

On Wed, Aug 14, 2013 at 1:46 PM, Eli Bendersky <eliben at google.com> wrote: > > Now get rid of pre-2.6 Python support ;-) Not only it helps clean-up code, > by 2-and-3 coexistence is much easier. > > It looks like Daniel was able to add py3k support fairly cleanly. I'm not sure how much of a difference removing pre-2.6 support would make at this point. (also, let's not start down the road of that discussion, as it has been quite incendiary in the past) -- Sean Silva -------------- next part -------------- An HTML attachment wa...

...extlinux: Avoid dereferencing a garbage pointer Merge branch 'searchdir_leak-406' of git://git.zytor.com/users/sha0/syslinux into stable isolinux: Update LBA in getlinsec loop version: bump version and date Paulo Alcantara (1): menugen: Make it compatible with Py3k Shao Miller (1): fs: Fix searchdir resource leak -- Matt Fleming, Intel Open Source Technology Center

.... 4. I'm not sure exactly how to markup the questions. The sphinx FAQ ( > http://sphinx.pocoo.org/faq.html) marks it up as a definition list > (ctrl-f "definition list" http://sphinx.pocoo.org/rest.html). On the > other hand, the Python FAQs (e.g. > http://docs.python.org/py3k/faq/general.html) do it differently, with > each question as a sub-section. I don't really know the "right answer", but > try to choose a style that has a precedent (and communicate the precedent > to reviewers). > Doing the definition list thing might work very well in t...

...cessarily forcing people to move to a different python 2.x version. > I believe that 2.6 was the first version that had the __future__ > import print_function available, which means that python 2.4 and 2.5 > would not be able to use print statements if they are to interoperate > with py3k. This is a very valid point. There are other options like e.g. the six python 2&3 compatibility library http://pypi.python.org/pypi/six, which supports python 2.4. It also provides a generic print statement. Using such a compatibility library could make sense in general. If it does, python 2.4...

...why, I have no clue. 4. I'm not sure exactly how to markup the questions. The sphinx FAQ ( http://sphinx.pocoo.org/faq.html) marks it up as a definition list (ctrl-f "definition list" http://sphinx.pocoo.org/rest.html). On the other hand, the Python FAQs (e.g. http://docs.python.org/py3k/faq/general.html) do it differently, with each question as a sub-section. I don't really know the "right answer", but try to choose a style that has a precedent (and communicate the precedent to reviewers). 5. kind of in line with the last point, choose "header styles" that...

Hi Sean, On 04/12/12 18:36, Sean Silva wrote: >> If there was a concrete need to move to a newer Python version in order to >> make lit Python 3 compatible, I would view that as a good reason to move >> forward. > > The concrete need is that users on platforms which ship with Python 3 > by default have to put in a workaround (install python2 and patch > their $PATH)

...garbage pointer Merge branch 'searchdir_leak-406' of git://git.zytor.com/users/sha0/syslinux into stable isolinux: Update LBA in getlinsec loop version: bump version and date NEWS: document changes in 4.07 Paulo Alcantara (1): menugen: Make it compatible with Py3k Shao Miller (1): fs: Fix searchdir resource leak -- Matt Fleming, Intel Open Source Technology Center

> If there was a concrete need to move to a newer Python version in order to > make lit Python 3 compatible, I would view that as a good reason to move > forward. The concrete need is that users on platforms which ship with Python 3 by default have to put in a workaround (install python2 and patch their $PATH) just to run the test suite. Off the top of my head I know this includes Ubuntu

...lines in ext2fs code and the other adds an assert() macro to Syslinux core. I think it's worth mentioning that these changes were made against master branch. Paulo The following changes since commit e40ba6059aa9c6b5cefd01e277eafbe60c7752fd: menugen: Make it compatible with Py3k (2013-02-27 21:38:11 +0000) are available in the git repository at: git://git.zytor.com/users/pcacjr/syslinux.git ext4-for-hpa for you to fetch changes up to 23045314f5897652b3002d2f9c07840b01d308a4: ext4: Add inline data support (2013-03-02 13:10:09 -0300) Signed-off-by: Paulo Cavalcanti...

...t; 4. I'm not sure exactly how to markup the questions. The sphinx FAQ ( > http://sphinx.pocoo.org/faq.html) marks it up as a definition list > (ctrl-f "definition list" http://sphinx.pocoo.org/rest.html). On the > other hand, the Python FAQs (e.g. > http://docs.python.org/py3k/faq/general.html) do it differently, with > each question as a sub-section. I don't really know the "right answer", but > try to choose a style that has a precedent (and communicate the precedent > to reviewers). > > 5. kind of in line with the last point, choose "...

I just finished up the first draft of the FAQ translated verbatim from HTML to Sphinx. Sphinx did puzzle me a few times but I got used to its approximate error messages and figured out what the problems were. Perhaps you could take a quick glance at this file and tell me if I am doing something wrong? Otherwise I'll send it off to llvm-commits and see what they say. Thanks, Mikael

> 8. A Technical Writer FAQ (should include the Sphinx documentation from the lld docs). I'm working on the Sphinx stuff; if you have any questions about writing Sphinx docs feel free to ask. --Sean Silva On Wed, Jun 13, 2012 at 4:37 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > I think the best way that I can currently contribute to the project is > through technical