From matti.picus at gmail.com Mon Jun 1 00:39:44 2015 From: matti.picus at gmail.com (Matti Picus) Date: Mon, 01 Jun 2015 01:39:44 +0300 Subject: [pypy-dev] PyPy 2.6.0 release binaries available (second try) Message-ID: <556B8DB0.9080200@gmail.com> New release packages with cffi 1.1.0 are available on bitbucket , note these are different than what I sent out before. https://bitbucket.org/pypy/pypy/downloads Please try them out, we have new buildslaves for win32, macosx and linux64. We would especially appreciate testing out the vmprof profiling features available on linux-64 Comments on the release notice are also welcome, extra points for guessing what "Cameo Charm" means. No fair checking IRC logs for hints. http://pypy.readthedocs.org/en/release-2.6.x/release-2.6.0.html Matti From arigo at tunes.org Mon Jun 1 12:13:32 2015 From: arigo at tunes.org (Armin Rigo) Date: Mon, 1 Jun 2015 12:13:32 +0200 Subject: [pypy-dev] PyPy 2.6.0 release binaries available (second try) In-Reply-To: <556B8DB0.9080200@gmail.com> References: <556B8DB0.9080200@gmail.com> Message-ID: Hi, On 1 June 2015 at 00:39, Matti Picus wrote: > We would especially appreciate testing out the vmprof profiling features > available on linux-64 See https://vmprof.readthedocs.org/ . Armin From donald at stufft.io Mon Jun 1 22:00:08 2015 From: donald at stufft.io (Donald Stufft) Date: Mon, 1 Jun 2015 16:00:08 -0400 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? Message-ID: Hey! So out of someone complaining about PyPy's lack of an up to date port of Python 3, it struck me that for someone just now looking into PyPy it looks like PyPy is sitting on almost 60k USD in order to port PyPy3 from 3.2 to 3.4. However the reality (via fijall) is that most of it, roughly 50k has already been spent going from nothing to 3.2. It might be a good idea to have the numbers reflect how much of the fundraised money has already been spent so that people get a more accurate reflection on just how much money there is left to take the task at hand from where it is now to where folks want it to be. My assumption is that people are going to feel a lot more like their money is going to be useful if it's not just adding onto the tail of what looks to be a fairly major pot of money and thus are more likely to actually donate. This of course doesn't just apply to Python 3 porting, the same thing is true for all of the fundraisers that PyPy is running. Without more information I have no way to evaluate if PyPy is sitting with cash reserves for that task and it's waiting for someone to work on it, or if it's mostly gone and it needs more funding to get any more effort applied to it. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA From donald at stufft.io Mon Jun 1 22:05:03 2015 From: donald at stufft.io (Donald Stufft) Date: Mon, 1 Jun 2015 16:05:03 -0400 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? In-Reply-To: References: Message-ID: On June 1, 2015 at 4:00:09 PM, Donald Stufft (donald at stufft.io) wrote: > Hey! > > So out of someone complaining about PyPy's lack of an up to date port of > Python 3, it struck me that for someone just now looking into PyPy it looks > like PyPy is sitting on almost 60k USD in order to port PyPy3 from 3.2 to 3.4. > However the reality (via fijall) is that most of it, roughly 50k has already > been spent going from nothing to 3.2. It might be a good idea to have the > numbers reflect how much of the fundraised money has already been spent so that > people get a more accurate reflection on just how much money there is left to > take the task at hand from where it is now to where folks want it to be. My > assumption is that people are going to feel a lot more like their money is > going to be useful if it's not just adding onto the tail of what looks to be > a fairly major pot of money and thus are more likely to actually donate. > > This of course doesn't just apply to Python 3 porting, the same thing is true > for all of the fundraisers that PyPy is running. Without more information I > have no way to evaluate if PyPy is sitting with cash reserves for that task > and it's waiting for someone to work on it, or if it's mostly gone and it needs > more funding to get any more effort applied to it. > Also, if you read the actual proposal for Python 3, the last update to it says: ? ? Thanks to our donors, we have raised 45% of the total so far. Work on this ? ? topic has been happening, and continues to happen, within the budget ? even ? ? if not within the timeline described below. We have simply not found enough ? ? time to work on it as much as we wanted, and thus did not consume the money ? ? as quickly as predicted. The ratio ?progress / $ used? so far corresponds ? ? roughly to what we expected. The document below is the original call for ? ? proposal, and we still accept donations for this topic. Which would read to me like it confirms the above, that there is a surplus of money just sitting around waiting for someone to actually get around to working on the port and spend that money. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA From hengha.mao at gmail.com Wed Jun 3 05:37:22 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Wed, 3 Jun 2015 11:37:22 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module Message-ID: Hi, Some builtin modules only expose interpreter level function, e.g. in builtin module select: appleveldefs = { } interpleveldefs = { 'select': 'interp_select.select', 'error' : 'space.fromcache(interp_select.Cache).w_error' } And for a new built model, how to import and use that interpreter level function in app level code? We tried to import the module in app level code, but failed. e.g., in a new built module: interpleveldefs = { } appleveldefs = { 'test_api': 'app_test.test_api', } In app_ test.py, we tried to import the module, but neither of below could succeed: import select => ImportError: No module named select import pypy.module.select =>ImportError: No module named pypy -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Wed Jun 3 08:49:52 2015 From: arigo at tunes.org (Armin Rigo) Date: Wed, 3 Jun 2015 08:49:52 +0200 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: Hi Yicong, On 3 June 2015 at 05:37, Yicong Huang wrote: > We tried to import the module in app level code, but failed. That's how it is done in various modules. See for example pypy/module/_collections/app_defaultdict. Maybe you wrote a test that did you start with: class AppTestTestAPI: spaceconfig = dict(usemodules=['modulename']) which is needed, otherwise the test runs in a configuration in which the module is not present. A bient?t, Armin. From lists at tinloaf.de Fri Jun 5 03:03:36 2015 From: lists at tinloaf.de (Lukas Barth) Date: Fri, 05 Jun 2015 03:03:36 +0200 Subject: [pypy-dev] Getting a backtrace out of the sandbox Message-ID: <5570F568.3090303@tinloaf.de> Hi everyone, I'm using the pypy sandbox, with a slightly modified pypy_interact.py script. Basically, I'm starting pypy-c with a '-c "from foo import bar\nbar()' command line argument instead of running a script directly. After that, I do sandproc.communicate("") to get the result of the script. Now, this all works fine. I only have a problem if there's a problem in the sandboxed script. If there's an exception, the only thing I get is a > OSError: the sandboxed subprocess exited with code 1 Is there any way of actually getting the backtrace? Thanks a lot, Lukas From kostia.lopuhin at gmail.com Fri Jun 5 09:22:24 2015 From: kostia.lopuhin at gmail.com (=?UTF-8?B?0JrQvtGB0YLRjyDQm9C+0L/Rg9GF0LjQvQ==?=) Date: Fri, 5 Jun 2015 10:22:24 +0300 Subject: [pypy-dev] Getting a backtrace out of the sandbox In-Reply-To: <5570F568.3090303@tinloaf.de> References: <5570F568.3090303@tinloaf.de> Message-ID: Hi! As far as I know, there is no built-in way, but you can catch all exceptions and send them to the parent process in the same way you send the result - this is what we do for our sandbox usecase. 2015-06-05 4:03 GMT+03:00 Lukas Barth : > Hi everyone, > > I'm using the pypy sandbox, with a slightly modified pypy_interact.py > script. Basically, I'm starting pypy-c with a '-c "from foo import > bar\nbar()' command line argument instead of running a script directly. > After that, I do sandproc.communicate("") to get the result of the script. > > Now, this all works fine. I only have a problem if there's a problem in > the sandboxed script. If there's an exception, the only thing I get is a > >> OSError: the sandboxed subprocess exited with code 1 > > Is there any way of actually getting the backtrace? > > Thanks a lot, > > Lukas > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev From arigo at tunes.org Fri Jun 5 09:35:42 2015 From: arigo at tunes.org (Armin Rigo) Date: Fri, 5 Jun 2015 09:35:42 +0200 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? In-Reply-To: References: Message-ID: Hi Donald, hi everybody, On 1 June 2015 at 22:00, Donald Stufft wrote: > So out of someone complaining about PyPy's lack of an up to date port of > Python 3, it struck me that for someone just now looking into PyPy it looks > like PyPy is sitting on almost 60k USD in order to port PyPy3 from 3.2 to 3.4. > However the reality (via fijall) is that most of it, roughly 50k has already > been spent going from nothing to 3.2. Thanks for bringing this up. I added to pypy.org the display of the amount left in our account for each project. Like the amount received, this number is updated from a source that depends on a manual step somewhere. This manual step is typically done only a few times per month. Don't be surprised if you donate and it does not show up immediately! Current situation: numpy: $52184 received, $15999 left py3k: $59578 received, $5045 left stm (2nd call): $29112 received, $22016 left We also have two Summer of Code projects, one related to numpy (performance via vectorization, not general compatibility) and one on py3k (planning a first 3.3 version by midterm, but knowing that 3.4 is the version most used, trying to push forward). STM is progressing too, but I am alone on consuming the funds and recently I've been "side-tracked" by CFFI 1.0 (coming back to STM now). A bient?t, Armin. From arigo at tunes.org Fri Jun 5 09:59:27 2015 From: arigo at tunes.org (Armin Rigo) Date: Fri, 5 Jun 2015 09:59:27 +0200 Subject: [pypy-dev] Getting a backtrace out of the sandbox In-Reply-To: References: <5570F568.3090303@tinloaf.de> Message-ID: Hi, On 5 June 2015 at 09:22, ????? ??????? wrote: > As far as I know, there is no built-in way, but you can catch all > exceptions and send them to the parent process in the same way you > send the result - this is what we do for our sandbox usecase. The subprocess should print the exception to it captured stderr, which the parent reads and returns in communicate(), no? Maybe I'm missing something. A bient?t, Armin. From kostia.lopuhin at gmail.com Fri Jun 5 11:31:14 2015 From: kostia.lopuhin at gmail.com (=?UTF-8?B?0JrQvtGB0YLRjyDQm9C+0L/Rg9GF0LjQvQ==?=) Date: Fri, 5 Jun 2015 12:31:14 +0300 Subject: [pypy-dev] Getting a backtrace out of the sandbox In-Reply-To: References: <5570F568.3090303@tinloaf.de> Message-ID: Yes, indeed, this is the easiest way, sorry for confusion! We process exception inside the sandbox in order to fix line numbers and remove some frames, so that information corresponds to what is seen by the author of the script - this is slightly easier to do inside the sandbox (no need to parse anything). 2015-06-05 10:59 GMT+03:00 Armin Rigo : > Hi, > > On 5 June 2015 at 09:22, ????? ??????? wrote: >> As far as I know, there is no built-in way, but you can catch all >> exceptions and send them to the parent process in the same way you >> send the result - this is what we do for our sandbox usecase. > > The subprocess should print the exception to it captured stderr, which > the parent reads and returns in communicate(), no? Maybe I'm missing > something. > > > A bient?t, > > Armin. From arigo at tunes.org Fri Jun 5 12:45:34 2015 From: arigo at tunes.org (Armin Rigo) Date: Fri, 5 Jun 2015 12:45:34 +0200 Subject: [pypy-dev] Getting a backtrace out of the sandbox In-Reply-To: References: <5570F568.3090303@tinloaf.de> Message-ID: Hi Kostia, On 5 June 2015 at 11:31, ????? ??????? wrote: > Yes, indeed, this is the easiest way, sorry for confusion! > We process exception inside the sandbox in order to fix line numbers > and remove some frames, so that information corresponds to what is > seen by the author of the script - this is slightly easier to do > inside the sandbox (no need to parse anything). Ok, I see! Thanks for the explanation. Armin From gmludo at gmail.com Sat Jun 6 07:23:38 2015 From: gmludo at gmail.com (Ludovic Gasc) Date: Sat, 6 Jun 2015 07:23:38 +0200 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? In-Reply-To: References: Message-ID: Hi, I don't know it should help, however European Commission has simplified the process to help SMEs for the innovation: http://ec.europa.eu/research/participants/portal/desktop/en/funding/sme_participation.html The constraint is to have a legal company in the European Union, it should be also a consortium if several companies around PyPy are interested in. All details: http://ec.europa.eu/research/participants/portal/desktop/en/support/faq.html#f16 I've received some feedbacks via my network about this funding, for now, it's an helpful operation. Moreover, European Commission is officially Open Source friendly: http://ec.europa.eu/dgs/informatics/oss_tech/index_en.htm Regards. -- Ludovic Gasc (GMLudo) http://www.gmludo.eu/ 2015-06-05 9:35 GMT+02:00 Armin Rigo : > Hi Donald, hi everybody, > > On 1 June 2015 at 22:00, Donald Stufft wrote: > > So out of someone complaining about PyPy's lack of an up to date port of > > Python 3, it struck me that for someone just now looking into PyPy it > looks > > like PyPy is sitting on almost 60k USD in order to port PyPy3 from 3.2 > to 3.4. > > However the reality (via fijall) is that most of it, roughly 50k has > already > > been spent going from nothing to 3.2. > > Thanks for bringing this up. I added to pypy.org the display of the > amount left in our account for each project. > > Like the amount received, this number is updated from a source that > depends on a manual step somewhere. This manual step is typically > done only a few times per month. Don't be surprised if you donate and > it does not show up immediately! > > Current situation: > > numpy: $52184 received, $15999 left > py3k: $59578 received, $5045 left > stm (2nd call): $29112 received, $22016 left > > We also have two Summer of Code projects, one related to numpy > (performance via vectorization, not general compatibility) and one on > py3k (planning a first 3.3 version by midterm, but knowing that 3.4 is > the version most used, trying to push forward). STM is progressing > too, but I am alone on consuming the funds and recently I've been > "side-tracked" by CFFI 1.0 (coming back to STM now). > > > A bient?t, > > Armin. > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmludo at gmail.com Sat Jun 6 08:09:01 2015 From: gmludo at gmail.com (Ludovic Gasc) Date: Sat, 6 Jun 2015 08:09:01 +0200 Subject: [pypy-dev] py3k and py3.3 branches Message-ID: Hi, I see more activity on py3k than py3.3. What the branch you recommend to test Python3 support of PyPy ? py3k ? The next stable release of PyPy3 will be based on py3.3 ? Regards. -- Ludovic Gasc (GMLudo) http://www.gmludo.eu/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengha.mao at gmail.com Sat Jun 6 08:34:07 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Sat, 6 Jun 2015 14:34:07 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: Hi Armin, Great thanks for the method! I had a try, but found it seemed only work for writing module tests, and failed for writing app level code for a new module. Here are what we tried: In the new module __init__.py, we defined app level code: appleveldefs = { 'tid': 'app_wrap.tid' } And in app_wrap.py, we tried to use "thread.get_ident()" from builtin module's interperter code: class wrapAPI: spaceconfig = dict(usemodules=['thread']) def thread_wrap(self): import thread return thread.get_ident() w = wrapAPI() def tid(): print w.thread_wrap() Finally, we wrote a pytest to test the module: import pytest class AppTest: spaceconfig = dict(usemodules=['wrap']) def test_wrap(self): import wrap print wrap.tid() The pytest failed and reported the error: def test_wrap(self): import wrap > print wrap.tid() E (application-level) ImportError: No module named thread >From the experiment, we still could not import and use the builtin module's function for writing a new module. On Wed, Jun 3, 2015 at 2:49 PM, Armin Rigo wrote: > Hi Yicong, > > On 3 June 2015 at 05:37, Yicong Huang wrote: > > We tried to import the module in app level code, but failed. > > That's how it is done in various modules. See for example > pypy/module/_collections/app_defaultdict. Maybe you wrote a test that > did you start with: > > class AppTestTestAPI: > spaceconfig = dict(usemodules=['modulename']) > > which is needed, otherwise the test runs in a configuration in which > the module is not present. > > > A bient?t, > > Armin. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Sat Jun 6 19:05:14 2015 From: arigo at tunes.org (Armin Rigo) Date: Sat, 6 Jun 2015 19:05:14 +0200 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: Hi Yicong, On 6 June 2015 at 08:34, Yicong Huang wrote: > class wrapAPI: > spaceconfig = dict(usemodules=['thread']) The "spaceconfig" is not something magic that applies to any class. Only the test runner knows about it, and the class must be called AppTestXxx in order for it to be picked up by the test runner (py.test). You must not instantiate it yourself. Armin From hengha.mao at gmail.com Sun Jun 7 09:33:55 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Sun, 7 Jun 2015 15:33:55 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: Hi Armin, >From your explanations, spaceconfig might not apply to write the module app code, but only for writing tests. In this case, any alternative methods? 1. Could app code use the interpreter code from the same module? If yes, I think we could wrap builtin module interterper function in interp_xxx.py, and then use in app_xxx.py. 2. From module's __init__.py, it is able to import pypy.module.xxxx. Could we write a funtion in __init__.py and then use ins app_xxx.py? On Sun, Jun 7, 2015 at 1:05 AM, Armin Rigo wrote: > Hi Yicong, > > On 6 June 2015 at 08:34, Yicong Huang wrote: > > class wrapAPI: > > spaceconfig = dict(usemodules=['thread']) > > The "spaceconfig" is not something magic that applies to any class. > Only the test runner knows about it, and the class must be called > AppTestXxx in order for it to be picked up by the test runner > (py.test). You must not instantiate it yourself. > > > Armin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Sun Jun 7 09:47:08 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 7 Jun 2015 09:47:08 +0200 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: Hi Yicong, On 7 June 2015 at 09:33, Yicong Huang wrote: > In this case, any alternative methods? I really think you need to look at some other directories "pypy/module/*/" and use the same style. I'm still unsure what you're trying to do, so I can't answer you more precisely. Most probably, it is similar to other existing modules. If it is too different from all of them, then you might be using entirely the wrong approach... A bient?t, Armin. From hengha.mao at gmail.com Mon Jun 8 13:22:23 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Mon, 8 Jun 2015 19:22:23 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: By reading modules in pypy/module, finally we found out the workaround method. For most of modules in 'pypy/module', their interp code could not be imported or used by other module's app code. But there is special module '__pypy__', it exposed several interp functions, and those code are used by other module's app code. E.g. __builtin__/app_functional.py used resizelist_hint and newlist_hint from __pypy__ module. But these two functions are actually defined as interp code in ?__pypy__' module. The workaround solution is simple: add one more interface in __pypy__ module's __init__.py and point to the interp file in the module that would expose. E.g. if we would like to use function from fcntl/interp_fcntl.py, add below lines: import pypy.module.fcntl.interp_fcntl interpleveldefs = { ... 'xxx' : 'pypy.module.interpfcntl.xxx'} And then the function is visible to app code of the module by: from __pypy__ import xxx And finally, here comes the question why __pypy__ module is special to be capable to expose interp code? For a quick glance, we observed some extra code in its __init__.py, which were not seen from other modules: PYC_MAGIC = get_pyc_magic(self.space) self.extra_interpdef('PYC_MAGIC', 'space.wrap(%d)' % PYC_MAGIC) Are the above code do the magic thing to expose interp code? On Sun, Jun 7, 2015 at 3:47 PM, Armin Rigo wrote: > Hi Yicong, > > On 7 June 2015 at 09:33, Yicong Huang wrote: > > In this case, any alternative methods? > > I really think you need to look at some other directories > "pypy/module/*/" and use the same style. I'm still unsure what you're > trying to do, so I can't answer you more precisely. Most probably, it > is similar to other existing modules. If it is too different from all > of them, then you might be using entirely the wrong approach... > > > A bient?t, > > Armin. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmitry at getgrist.com Tue Jun 9 00:31:35 2015 From: dmitry at getgrist.com (Dmitry Sagalovskiy) Date: Mon, 8 Jun 2015 18:31:35 -0400 Subject: [pypy-dev] Sandbox missing functions like 'fcntl' Message-ID: Hi! I am getting this error from the sandbox: Not Implemented: sandboxing for external function 'fcntl' I am using a custom controller process, and getting this in fdopen (pypy_interact bombs on something else before it gets to that point). After much digging, I think this is due to _check_fd_mode function in rpython/rlib/streamio.py. In sandbox mode, I think there is little use for this check, but since it's there, I need some workaround. Does anyone have recommendations? More generally, my team needs to decide if we can rely on the pypy sandbox to use in our product. It seems brilliantly designed, fast, and overall impressive. But there are these gaps in missing sandbox wrappers (there are others too, fcntl is just one that I don't know how to avoid). And I noticed some code that indicates that it is not supported on Windows -- is that the case? What are the sandbox's prospects, within the larger future of pypy? Dmitry -------------- next part -------------- An HTML attachment was scrubbed... URL: From william.leslie.ttg at gmail.com Tue Jun 9 03:30:05 2015 From: william.leslie.ttg at gmail.com (William ML Leslie) Date: Tue, 9 Jun 2015 11:30:05 +1000 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: On 8 June 2015 at 21:22, Yicong Huang wrote: > By reading modules in pypy/module, finally we found out the workaround > method. > > For most of modules in 'pypy/module', their interp code could not be > imported or used by other module's app code. > But there is special module '__pypy__', it exposed several interp > functions, and those code are used by other module's app code. > ?There's nothing special about __pypy__ for exposing interp-level code, the modules in pypy/modules? usually include interp level code. ?For example, the select module exposes the interp-level function select_interp.select. Here's how it does so: ? https://bitbucket.org/pypy/pypy/src/b0c01840baea472c834635de627bb596c05d3bd5/pypy/module/select/__init__.py?at=default The interpreter gateway has more options for exposing interp-level functions and types to app-level?. The workaround solution is simple: add one more interface in __pypy__ > module's __init__.py > ?You should make a new module rather than adding to one existing one.? > PYC_MAGIC = get_pyc_magic(self.space) self.extra_interpdef('PYC_MAGIC', 'space.wrap(%d)' % PYC_MAGIC) > Are the above code do the magic thing to expose interp code? > ?They are exposing an integer value called PYC_MAGIC, which is the value for determining what python the .pyc file was compiled for.? ?This is about exposing an integer rather than a function, it's probably not relevant to you. -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely MAY reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without prior contractual agreement. -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmitry at getgrist.com Tue Jun 9 05:10:53 2015 From: dmitry at getgrist.com (Dmitry Sagalovskiy) Date: Mon, 8 Jun 2015 23:10:53 -0400 Subject: [pypy-dev] Sandbox missing functions like 'fcntl' In-Reply-To: References: Message-ID: Here is a far more baffling one: Not Implemented: sandboxing for external function 'pypy_jit_depthmap_add' That's certainly not something I would expect the controller process to implement. It seems to happen after a bunch of repetitive commands (when I suppose JIT is kicking in). BTW, I did not run into either of these issues with a build from a year ago, around commit 72100. If anyone can suggest what I might be doing wrong, I would greatly appreciate. Dmitry On Mon, Jun 8, 2015 at 6:31 PM, Dmitry Sagalovskiy wrote: > Hi! > > I am getting this error from the sandbox: > > Not Implemented: sandboxing for external function 'fcntl' > > I am using a custom controller process, and getting this in fdopen > (pypy_interact bombs on something else before it gets to that point). After > much digging, I think this is due to _check_fd_mode function in > rpython/rlib/streamio.py. In sandbox mode, I think there is little use for > this check, but since it's there, I need some workaround. Does anyone have > recommendations? > > More generally, my team needs to decide if we can rely on the pypy sandbox > to use in our product. It seems brilliantly designed, fast, and overall > impressive. But there are these gaps in missing sandbox wrappers (there are > others too, fcntl is just one that I don't know how to avoid). And I > noticed some code that indicates that it is not supported on Windows -- is > that the case? > > What are the sandbox's prospects, within the larger future of pypy? > > Dmitry > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Tue Jun 9 08:46:59 2015 From: arigo at tunes.org (Armin Rigo) Date: Tue, 9 Jun 2015 08:46:59 +0200 Subject: [pypy-dev] Sandbox missing functions like 'fcntl' In-Reply-To: References: Message-ID: Hi Dmitry, On 9 June 2015 at 05:10, Dmitry Sagalovskiy wrote: > More generally, my team needs to decide if we can rely on the pypy sandbox to use in our product. It seems brilliantly designed, fast, and overall impressive. But there are these gaps in missing sandbox wrappers (there are others too, fcntl is just one that I don't know how to avoid). And I noticed some code that indicates that it is not supported on Windows -- is that the case? > What are the sandbox's prospects, within the larger future of pypy? The sandbox code is there and "mostly working", but it is lacking a champion. It has been in this state for many years now (it is actually impressive that it still roughly works). Realistically, though, to answer the question of its prospects, it depends entirely on whether someone would be ready to become involved in PyPy and help maintain and develop it. As usual with Open Source, we can't predict when (and if) this will occur. From our point of view, it seems to attract occasional attention like yours, but we just have too many things to work on. > If anyone can suggest what I might be doing wrong, I would greatly > appreciate. You're not doing anything wrong, just stumbling on a mixture of old and new code. In the case of 'pypy_jit_depthmap_add', it's because we recently added vmprof support and didn't think about sandboxing. The fix is probably easy: we need a few "sandboxsafe=True" keyword arguments in rpython/jit/backend/llsupport/codemap.py. The issue with 'fcntl' is more obscure and involves much older code. In that case we need the sandboxed interpreter to ask the outside what to do---which should occur automatically, but doesn't, for reasons I'm still investigating. I suspect it's related to the XXX in the comment of select_function_code_generators() in rpython.translator.c.node. (I think with minimal effort we can finally get rid of the "oldstyle" functions mentioned there.) A bient?t, Armin. From hengha.mao at gmail.com Tue Jun 9 10:20:22 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Tue, 9 Jun 2015 16:20:22 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: "The interpreter gateway has more options for exposing interp-level functions and types to app-level?." How does this work? We tried several builtin modules, as well as "select" module that you mentioned, all thses modules's interp-level code are invisble to other module's app-level. We would like to take your advices to make a new module. But the problem is how to make the new module's interp-level code visible to app-level? On Tue, Jun 9, 2015 at 9:30 AM, William ML Leslie < william.leslie.ttg at gmail.com> wrote: > On 8 June 2015 at 21:22, Yicong Huang wrote: > >> By reading modules in pypy/module, finally we found out the workaround >> method. >> >> For most of modules in 'pypy/module', their interp code could not be >> imported or used by other module's app code. >> But there is special module '__pypy__', it exposed several interp >> functions, and those code are used by other module's app code. >> > > ?There's nothing special about __pypy__ for exposing interp-level code, > the modules in pypy/modules? usually include interp level code. > > ?For example, the select module exposes the interp-level function > select_interp.select. Here's how it does so: > > ? > https://bitbucket.org/pypy/pypy/src/b0c01840baea472c834635de627bb596c05d3bd5/pypy/module/select/__init__.py?at=default > > The interpreter gateway has more options for exposing interp-level > functions and types to app-level?. > > The workaround solution is simple: add one more interface in __pypy__ >> module's __init__.py >> > > ?You should make a new module rather than adding to one existing one.? > > >> PYC_MAGIC = get_pyc_magic(self.space) > > self.extra_interpdef('PYC_MAGIC', 'space.wrap(%d)' % PYC_MAGIC) > > >> Are the above code do the magic thing to expose interp code? >> > > ?They are exposing an integer value called PYC_MAGIC, which is the value > for determining what python the .pyc file was compiled for.? > > ?This is about exposing an integer rather than a function, it's probably > not relevant to you. > > > -- > William Leslie > > Notice: > Likely much of this email is, by the nature of copyright, covered under > copyright law. You absolutely MAY reproduce any part of it in accordance > with the copyright law of the nation you are reading this in. Any attempt > to DENY YOU THOSE RIGHTS would be illegal without prior contractual > agreement. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Tue Jun 9 10:25:40 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Tue, 9 Jun 2015 10:25:40 +0200 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: 2015-06-09 10:20 GMT+02:00 Yicong Huang : > "The interpreter gateway has more options for exposing interp-level > functions and types to app-level?." > > How does this work? > We tried several builtin modules, as well as "select" module that you > mentioned, all thses modules's interp-level code are invisble to other > module's app-level. > > We would like to take your advices to make a new module. But the problem > is how to make the new module's interp-level code visible to app-level? > See the "posix" module for example. Most functions are defined at interp-level, but there is also a file "app_posix.py" which just does "import posix" and happily calls interp-level code. > > > On Tue, Jun 9, 2015 at 9:30 AM, William ML Leslie < > william.leslie.ttg at gmail.com> wrote: > >> On 8 June 2015 at 21:22, Yicong Huang wrote: >> >>> By reading modules in pypy/module, finally we found out the workaround >>> method. >>> >>> For most of modules in 'pypy/module', their interp code could not be >>> imported or used by other module's app code. >>> But there is special module '__pypy__', it exposed several interp >>> functions, and those code are used by other module's app code. >>> >> >> ?There's nothing special about __pypy__ for exposing interp-level code, >> the modules in pypy/modules? usually include interp level code. >> >> ?For example, the select module exposes the interp-level function >> select_interp.select. Here's how it does so: >> >> ? >> https://bitbucket.org/pypy/pypy/src/b0c01840baea472c834635de627bb596c05d3bd5/pypy/module/select/__init__.py?at=default >> >> The interpreter gateway has more options for exposing interp-level >> functions and types to app-level?. >> >> The workaround solution is simple: add one more interface in __pypy__ >>> module's __init__.py >>> >> >> ?You should make a new module rather than adding to one existing one.? >> >> >>> PYC_MAGIC = get_pyc_magic(self.space) >> >> self.extra_interpdef('PYC_MAGIC', 'space.wrap(%d)' % PYC_MAGIC) >> >> >>> Are the above code do the magic thing to expose interp code? >>> >> >> ?They are exposing an integer value called PYC_MAGIC, which is the value >> for determining what python the .pyc file was compiled for.? >> >> ?This is about exposing an integer rather than a function, it's probably >> not relevant to you. >> >> >> -- >> William Leslie >> >> Notice: >> Likely much of this email is, by the nature of copyright, covered under >> copyright law. You absolutely MAY reproduce any part of it in accordance >> with the copyright law of the nation you are reading this in. Any attempt >> to DENY YOU THOSE RIGHTS would be illegal without prior contractual >> agreement. >> > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengha.mao at gmail.com Tue Jun 9 11:15:28 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Tue, 9 Jun 2015 17:15:28 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: Great thanks! "posix" module is a good example. But this interp code reference is in the same module. How about a new module's app code to use interp code from other module? One method to follow "posix" example is to define interp code in the same module and wrap the interp function from other module for app code in the same module to use. But I observed __pypy__ module is different. Interp functions of _pypy_ module could be directly import in app code for other modules. We are curious how does it work? On Tue, Jun 9, 2015 at 4:25 PM, Amaury Forgeot d'Arc wrote: > 2015-06-09 10:20 GMT+02:00 Yicong Huang : > >> "The interpreter gateway has more options for exposing interp-level >> functions and types to app-level?." >> >> How does this work? >> We tried several builtin modules, as well as "select" module that you >> mentioned, all thses modules's interp-level code are invisble to other >> module's app-level. >> >> We would like to take your advices to make a new module. But the problem >> is how to make the new module's interp-level code visible to app-level? >> > > See the "posix" module for example. Most functions are defined at > interp-level, > but there is also a file "app_posix.py" which just does "import posix" and > happily calls interp-level code. > > > >> >> >> On Tue, Jun 9, 2015 at 9:30 AM, William ML Leslie < >> william.leslie.ttg at gmail.com> wrote: >> >>> On 8 June 2015 at 21:22, Yicong Huang wrote: >>> >>>> By reading modules in pypy/module, finally we found out the workaround >>>> method. >>>> >>>> For most of modules in 'pypy/module', their interp code could not be >>>> imported or used by other module's app code. >>>> But there is special module '__pypy__', it exposed several interp >>>> functions, and those code are used by other module's app code. >>>> >>> >>> ?There's nothing special about __pypy__ for exposing interp-level code, >>> the modules in pypy/modules? usually include interp level code. >>> >>> ?For example, the select module exposes the interp-level function >>> select_interp.select. Here's how it does so: >>> >>> ? >>> https://bitbucket.org/pypy/pypy/src/b0c01840baea472c834635de627bb596c05d3bd5/pypy/module/select/__init__.py?at=default >>> >>> The interpreter gateway has more options for exposing interp-level >>> functions and types to app-level?. >>> >>> The workaround solution is simple: add one more interface in __pypy__ >>>> module's __init__.py >>>> >>> >>> ?You should make a new module rather than adding to one existing one.? >>> >>> >>>> PYC_MAGIC = get_pyc_magic(self.space) >>> >>> self.extra_interpdef('PYC_MAGIC', 'space.wrap(%d)' % PYC_MAGIC) >>> >>> >>>> Are the above code do the magic thing to expose interp code? >>>> >>> >>> ?They are exposing an integer value called PYC_MAGIC, which is the value >>> for determining what python the .pyc file was compiled for.? >>> >>> ?This is about exposing an integer rather than a function, it's probably >>> not relevant to you. >>> >>> >>> -- >>> William Leslie >>> >>> Notice: >>> Likely much of this email is, by the nature of copyright, covered under >>> copyright law. You absolutely MAY reproduce any part of it in accordance >>> with the copyright law of the nation you are reading this in. Any attempt >>> to DENY YOU THOSE RIGHTS would be illegal without prior contractual >>> agreement. >>> >> >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> >> > > > -- > Amaury Forgeot d'Arc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Tue Jun 9 11:27:26 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Tue, 9 Jun 2015 11:27:26 +0200 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: 2015-06-09 11:15 GMT+02:00 Yicong Huang : > Great thanks! > "posix" module is a good example. But this interp code reference is in the > same module. > > How about a new module's app code to use interp code from other module? > One method to follow "posix" example is to define interp code in the same > module and wrap the interp function from other module for app code in the > same module to use. > This is not clear to me. Are you trying to call interp code from interp code? Then just import the interp module (pypy.module.xxx.yyy) > > But I observed __pypy__ module is different. Interp functions of _pypy_ > module could be directly import in app code for other modules. > We are curious how does it work? > > > > On Tue, Jun 9, 2015 at 4:25 PM, Amaury Forgeot d'Arc > wrote: > >> 2015-06-09 10:20 GMT+02:00 Yicong Huang : >> >>> "The interpreter gateway has more options for exposing interp-level >>> functions and types to app-level?." >>> >>> How does this work? >>> We tried several builtin modules, as well as "select" module that you >>> mentioned, all thses modules's interp-level code are invisble to other >>> module's app-level. >>> >>> We would like to take your advices to make a new module. But the problem >>> is how to make the new module's interp-level code visible to app-level? >>> >> >> See the "posix" module for example. Most functions are defined at >> interp-level, >> but there is also a file "app_posix.py" which just does "import posix" >> and happily calls interp-level code. >> >> >> >>> >>> >>> On Tue, Jun 9, 2015 at 9:30 AM, William ML Leslie < >>> william.leslie.ttg at gmail.com> wrote: >>> >>>> On 8 June 2015 at 21:22, Yicong Huang wrote: >>>> >>>>> By reading modules in pypy/module, finally we found out the workaround >>>>> method. >>>>> >>>>> For most of modules in 'pypy/module', their interp code could not be >>>>> imported or used by other module's app code. >>>>> But there is special module '__pypy__', it exposed several interp >>>>> functions, and those code are used by other module's app code. >>>>> >>>> >>>> ?There's nothing special about __pypy__ for exposing interp-level code, >>>> the modules in pypy/modules? usually include interp level code. >>>> >>>> ?For example, the select module exposes the interp-level function >>>> select_interp.select. Here's how it does so: >>>> >>>> ? >>>> https://bitbucket.org/pypy/pypy/src/b0c01840baea472c834635de627bb596c05d3bd5/pypy/module/select/__init__.py?at=default >>>> >>>> The interpreter gateway has more options for exposing interp-level >>>> functions and types to app-level?. >>>> >>>> The workaround solution is simple: add one more interface in __pypy__ >>>>> module's __init__.py >>>>> >>>> >>>> ?You should make a new module rather than adding to one existing one.? >>>> >>>> >>>>> PYC_MAGIC = get_pyc_magic(self.space) >>>> >>>> self.extra_interpdef('PYC_MAGIC', 'space.wrap(%d)' % PYC_MAGIC) >>>> >>>> >>>>> Are the above code do the magic thing to expose interp code? >>>>> >>>> >>>> ?They are exposing an integer value called PYC_MAGIC, which is the >>>> value for determining what python the .pyc file was compiled for.? >>>> >>>> ?This is about exposing an integer rather than a function, it's >>>> probably not relevant to you. >>>> >>>> >>>> -- >>>> William Leslie >>>> >>>> Notice: >>>> Likely much of this email is, by the nature of copyright, covered under >>>> copyright law. You absolutely MAY reproduce any part of it in accordance >>>> with the copyright law of the nation you are reading this in. Any attempt >>>> to DENY YOU THOSE RIGHTS would be illegal without prior contractual >>>> agreement. >>>> >>> >>> >>> _______________________________________________ >>> pypy-dev mailing list >>> pypy-dev at python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >>> >>> >> >> >> -- >> Amaury Forgeot d'Arc >> > > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengha.mao at gmail.com Tue Jun 9 11:34:41 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Tue, 9 Jun 2015 17:34:41 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: No, I' am trying to call interp code from app code, and found the module could not be imported: import select => ImportError: No module named select import pypy.module.select =>ImportError: No module named pypy But __pypy__ module is able to be imported. On Tue, Jun 9, 2015 at 5:27 PM, Amaury Forgeot d'Arc wrote: > 2015-06-09 11:15 GMT+02:00 Yicong Huang : > >> Great thanks! >> "posix" module is a good example. But this interp code reference is in >> the same module. >> >> How about a new module's app code to use interp code from other module? >> One method to follow "posix" example is to define interp code in the same >> module and wrap the interp function from other module for app code in the >> same module to use. >> > > This is not clear to me. > Are you trying to call interp code from interp code? Then just import the > interp module (pypy.module.xxx.yyy) > > >> >> But I observed __pypy__ module is different. Interp functions of _pypy_ >> module could be directly import in app code for other modules. >> We are curious how does it work? >> >> >> >> On Tue, Jun 9, 2015 at 4:25 PM, Amaury Forgeot d'Arc >> wrote: >> >>> 2015-06-09 10:20 GMT+02:00 Yicong Huang : >>> >>>> "The interpreter gateway has more options for exposing interp-level >>>> functions and types to app-level?." >>>> >>>> How does this work? >>>> We tried several builtin modules, as well as "select" module that you >>>> mentioned, all thses modules's interp-level code are invisble to other >>>> module's app-level. >>>> >>>> We would like to take your advices to make a new module. But the >>>> problem is how to make the new module's interp-level code visible to >>>> app-level? >>>> >>> >>> See the "posix" module for example. Most functions are defined at >>> interp-level, >>> but there is also a file "app_posix.py" which just does "import posix" >>> and happily calls interp-level code. >>> >>> >>> >>>> >>>> >>>> On Tue, Jun 9, 2015 at 9:30 AM, William ML Leslie < >>>> william.leslie.ttg at gmail.com> wrote: >>>> >>>>> On 8 June 2015 at 21:22, Yicong Huang wrote: >>>>> >>>>>> By reading modules in pypy/module, finally we found out the >>>>>> workaround method. >>>>>> >>>>>> For most of modules in 'pypy/module', their interp code could not be >>>>>> imported or used by other module's app code. >>>>>> But there is special module '__pypy__', it exposed several interp >>>>>> functions, and those code are used by other module's app code. >>>>>> >>>>> >>>>> ?There's nothing special about __pypy__ for exposing interp-level >>>>> code, the modules in pypy/modules? usually include interp level code. >>>>> >>>>> ?For example, the select module exposes the interp-level function >>>>> select_interp.select. Here's how it does so: >>>>> >>>>> ? >>>>> https://bitbucket.org/pypy/pypy/src/b0c01840baea472c834635de627bb596c05d3bd5/pypy/module/select/__init__.py?at=default >>>>> >>>>> The interpreter gateway has more options for exposing interp-level >>>>> functions and types to app-level?. >>>>> >>>>> The workaround solution is simple: add one more interface in __pypy__ >>>>>> module's __init__.py >>>>>> >>>>> >>>>> ?You should make a new module rather than adding to one existing one.? >>>>> >>>>> >>>>>> PYC_MAGIC = get_pyc_magic(self.space) >>>>> >>>>> self.extra_interpdef('PYC_MAGIC', 'space.wrap(%d)' % PYC_MAGIC) >>>>> >>>>> >>>>>> Are the above code do the magic thing to expose interp code? >>>>>> >>>>> >>>>> ?They are exposing an integer value called PYC_MAGIC, which is the >>>>> value for determining what python the .pyc file was compiled for.? >>>>> >>>>> ?This is about exposing an integer rather than a function, it's >>>>> probably not relevant to you. >>>>> >>>>> >>>>> -- >>>>> William Leslie >>>>> >>>>> Notice: >>>>> Likely much of this email is, by the nature of copyright, covered >>>>> under copyright law. You absolutely MAY reproduce any part of it in >>>>> accordance with the copyright law of the nation you are reading this in. >>>>> Any attempt to DENY YOU THOSE RIGHTS would be illegal without prior >>>>> contractual agreement. >>>>> >>>> >>>> >>>> _______________________________________________ >>>> pypy-dev mailing list >>>> pypy-dev at python.org >>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>> >>>> >>> >>> >>> -- >>> Amaury Forgeot d'Arc >>> >> >> > > > -- > Amaury Forgeot d'Arc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Tue Jun 9 11:39:00 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Tue, 9 Jun 2015 11:39:00 +0200 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: 2015-06-09 11:34 GMT+02:00 Yicong Huang : > No, I' am trying to call interp code from app code, and found the module > could not be imported: > > import select => ImportError: No module named select > import pypy.module.select =>ImportError: No module named pypy > "import select" is the one which should work at applevel. But for this, the PyPy object space must have the option "spaceconfig = dict(usemodules=['select'])", or be translated with --withmod-select. In which context are you running the code above? > > But __pypy__ module is able to be imported. > some modules are always selected: sys, posix, __pypy__... that's why you see a difference here. Put usemodules=['select'], somewhere. > > On Tue, Jun 9, 2015 at 5:27 PM, Amaury Forgeot d'Arc > wrote: > >> 2015-06-09 11:15 GMT+02:00 Yicong Huang : >> >>> Great thanks! >>> "posix" module is a good example. But this interp code reference is in >>> the same module. >>> >>> How about a new module's app code to use interp code from other module? >>> One method to follow "posix" example is to define interp code in the >>> same module and wrap the interp function from other module for app code in >>> the same module to use. >>> >> >> This is not clear to me. >> Are you trying to call interp code from interp code? Then just import the >> interp module (pypy.module.xxx.yyy) >> >> >>> >>> But I observed __pypy__ module is different. Interp functions of _pypy_ >>> module could be directly import in app code for other modules. >>> We are curious how does it work? >>> >>> >>> >>> On Tue, Jun 9, 2015 at 4:25 PM, Amaury Forgeot d'Arc >> > wrote: >>> >>>> 2015-06-09 10:20 GMT+02:00 Yicong Huang : >>>> >>>>> "The interpreter gateway has more options for exposing interp-level >>>>> functions and types to app-level?." >>>>> >>>>> How does this work? >>>>> We tried several builtin modules, as well as "select" module that you >>>>> mentioned, all thses modules's interp-level code are invisble to other >>>>> module's app-level. >>>>> >>>>> We would like to take your advices to make a new module. But the >>>>> problem is how to make the new module's interp-level code visible to >>>>> app-level? >>>>> >>>> >>>> See the "posix" module for example. Most functions are defined at >>>> interp-level, >>>> but there is also a file "app_posix.py" which just does "import posix" >>>> and happily calls interp-level code. >>>> >>>> >>>> >>>>> >>>>> >>>>> On Tue, Jun 9, 2015 at 9:30 AM, William ML Leslie < >>>>> william.leslie.ttg at gmail.com> wrote: >>>>> >>>>>> On 8 June 2015 at 21:22, Yicong Huang wrote: >>>>>> >>>>>>> By reading modules in pypy/module, finally we found out the >>>>>>> workaround method. >>>>>>> >>>>>>> For most of modules in 'pypy/module', their interp code could not be >>>>>>> imported or used by other module's app code. >>>>>>> But there is special module '__pypy__', it exposed several interp >>>>>>> functions, and those code are used by other module's app code. >>>>>>> >>>>>> >>>>>> ?There's nothing special about __pypy__ for exposing interp-level >>>>>> code, the modules in pypy/modules? usually include interp level code. >>>>>> >>>>>> ?For example, the select module exposes the interp-level function >>>>>> select_interp.select. Here's how it does so: >>>>>> >>>>>> ? >>>>>> https://bitbucket.org/pypy/pypy/src/b0c01840baea472c834635de627bb596c05d3bd5/pypy/module/select/__init__.py?at=default >>>>>> >>>>>> The interpreter gateway has more options for exposing interp-level >>>>>> functions and types to app-level?. >>>>>> >>>>>> The workaround solution is simple: add one more interface in __pypy__ >>>>>>> module's __init__.py >>>>>>> >>>>>> >>>>>> ?You should make a new module rather than adding to one existing one.? >>>>>> >>>>>> >>>>>>> PYC_MAGIC = get_pyc_magic(self.space) >>>>>> >>>>>> self.extra_interpdef('PYC_MAGIC', 'space.wrap(%d)' % PYC_MAGIC) >>>>>> >>>>>> >>>>>>> Are the above code do the magic thing to expose interp code? >>>>>>> >>>>>> >>>>>> ?They are exposing an integer value called PYC_MAGIC, which is the >>>>>> value for determining what python the .pyc file was compiled for.? >>>>>> >>>>>> ?This is about exposing an integer rather than a function, it's >>>>>> probably not relevant to you. >>>>>> >>>>>> >>>>>> -- >>>>>> William Leslie >>>>>> >>>>>> Notice: >>>>>> Likely much of this email is, by the nature of copyright, covered >>>>>> under copyright law. You absolutely MAY reproduce any part of it in >>>>>> accordance with the copyright law of the nation you are reading this in. >>>>>> Any attempt to DENY YOU THOSE RIGHTS would be illegal without prior >>>>>> contractual agreement. >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> pypy-dev mailing list >>>>> pypy-dev at python.org >>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Amaury Forgeot d'Arc >>>> >>> >>> >> >> >> -- >> Amaury Forgeot d'Arc >> > > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Tue Jun 9 11:38:45 2015 From: arigo at tunes.org (Armin Rigo) Date: Tue, 9 Jun 2015 11:38:45 +0200 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: Hi, On 9 June 2015 at 11:34, Yicong Huang wrote: > import select => ImportError: No module named select > import pypy.module.select =>ImportError: No module named pypy > > But __pypy__ module is able to be imported. I guess it's because __pypy__ is always enabled, but other modules can be enabled or disabled (for example using "spaceconfig" if you're writing tests in the same style as ours). A bient?t, Armin. From hengha.mao at gmail.com Tue Jun 9 11:51:56 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Tue, 9 Jun 2015 17:51:56 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: "I guess it's because __pypy__ is always enabled, but other modules can be enabled or disabled" How to enable the module? We had tried "spaceconfig", but it only worked for writing tests. On Tue, Jun 9, 2015 at 5:38 PM, Armin Rigo wrote: > Hi, > > On 9 June 2015 at 11:34, Yicong Huang wrote: > > import select => ImportError: No module named select > > import pypy.module.select =>ImportError: No module named pypy > > > > But __pypy__ module is able to be imported. > > I guess it's because __pypy__ is always enabled, but other modules can > be enabled or disabled (for example using "spaceconfig" if you're > writing tests in the same style as ours). > > > A bient?t, > > Armin. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Tue Jun 9 11:57:42 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Tue, 9 Jun 2015 11:57:42 +0200 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: 2015-06-09 11:51 GMT+02:00 Yicong Huang : > "I guess it's because __pypy__ is always enabled, but other modules can > be enabled or disabled" > > How to enable the module? > We had tried "spaceconfig", but it only worked for writing tests. > Again, how are you running PyPy? If it is the compiled binary, you need to pass --withmod-select at translation time. Same thing, if you started the (slow) untranslated bin/pyinteractive.py > > On Tue, Jun 9, 2015 at 5:38 PM, Armin Rigo wrote: > >> Hi, >> >> On 9 June 2015 at 11:34, Yicong Huang wrote: >> > import select => ImportError: No module named select >> > import pypy.module.select =>ImportError: No module named pypy >> > >> > But __pypy__ module is able to be imported. >> >> I guess it's because __pypy__ is always enabled, but other modules can >> be enabled or disabled (for example using "spaceconfig" if you're >> writing tests in the same style as ours). >> >> >> A bient?t, >> >> Armin. >> > > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengha.mao at gmail.com Tue Jun 9 12:04:43 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Tue, 9 Jun 2015 18:04:43 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: We used the compiled binary, and had added the option. We checked libpypy-c.so, it includs the symbols of "select". In addition, in pypy console we are able to import "select" module. However, all the above could not help the problem. On Tue, Jun 9, 2015 at 5:57 PM, Amaury Forgeot d'Arc wrote: > 2015-06-09 11:51 GMT+02:00 Yicong Huang : > >> "I guess it's because __pypy__ is always enabled, but other modules can >> be enabled or disabled" >> >> How to enable the module? >> We had tried "spaceconfig", but it only worked for writing tests. >> > > Again, how are you running PyPy? > If it is the compiled binary, you need to pass --withmod-select at > translation time. > Same thing, if you started the (slow) untranslated bin/pyinteractive.py > > >> >> On Tue, Jun 9, 2015 at 5:38 PM, Armin Rigo wrote: >> >>> Hi, >>> >>> On 9 June 2015 at 11:34, Yicong Huang wrote: >>> > import select => ImportError: No module named select >>> > import pypy.module.select =>ImportError: No module named pypy >>> > >>> > But __pypy__ module is able to be imported. >>> >>> I guess it's because __pypy__ is always enabled, but other modules can >>> be enabled or disabled (for example using "spaceconfig" if you're >>> writing tests in the same style as ours). >>> >>> >>> A bient?t, >>> >>> Armin. >>> >> >> > > > -- > Amaury Forgeot d'Arc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From william.leslie.ttg at gmail.com Tue Jun 9 13:21:15 2015 From: william.leslie.ttg at gmail.com (William ML Leslie) Date: Tue, 9 Jun 2015 21:21:15 +1000 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: On 9 June 2015 at 19:39, Amaury Forgeot d'Arc wrote: > 2015-06-09 11:34 GMT+02:00 Yicong Huang : > >> No, I' am trying to call interp code from app code, and found the module >> could not be imported: >> >> import select => ImportError: No module named select >> import pypy.module.select =>ImportError: No module named pypy >> > > "import select" is the one which should work at applevel. > But for this, the PyPy object space must have the option "spaceconfig = > dict(usemodules=['select'])", or be translated with --withmod-select. > In which context are you running the code above? > ?Are you using a pypy sandbox Huang? ?If so, many built-in modules are disabled by default, you have to enable them during translation. -- William Leslie Notice: Likely much of this email is, by the nature of copyright, covered under copyright law. You absolutely MAY reproduce any part of it in accordance with the copyright law of the nation you are reading this in. Any attempt to DENY YOU THOSE RIGHTS would be illegal without prior contractual agreement. -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengha.mao at gmail.com Tue Jun 9 13:52:31 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Tue, 9 Jun 2015 19:52:31 +0800 Subject: [pypy-dev] How to use interperter level code from a module for app level code in another module In-Reply-To: References: Message-ID: No, we used the normal build, not sandbox. And "select" option is by default enabled. On Tue, Jun 9, 2015 at 7:21 PM, William ML Leslie < william.leslie.ttg at gmail.com> wrote: > On 9 June 2015 at 19:39, Amaury Forgeot d'Arc wrote: > >> 2015-06-09 11:34 GMT+02:00 Yicong Huang : >> >>> No, I' am trying to call interp code from app code, and found the module >>> could not be imported: >>> >>> import select => ImportError: No module named select >>> import pypy.module.select =>ImportError: No module named pypy >>> >> >> "import select" is the one which should work at applevel. >> But for this, the PyPy object space must have the option "spaceconfig = >> dict(usemodules=['select'])", or be translated with --withmod-select. >> In which context are you running the code above? >> > > ?Are you using a pypy sandbox Huang? > > ?If so, many built-in modules are disabled by default, you have to enable > them during translation. > > -- > William Leslie > > Notice: > Likely much of this email is, by the nature of copyright, covered under > copyright law. You absolutely MAY reproduce any part of it in accordance > with the copyright law of the nation you are reading this in. Any attempt > to DENY YOU THOSE RIGHTS would be illegal without prior contractual > agreement. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dmitry at getgrist.com Tue Jun 9 16:35:28 2015 From: dmitry at getgrist.com (Dmitry Sagalovskiy) Date: Tue, 9 Jun 2015 10:35:28 -0400 Subject: [pypy-dev] Sandbox missing functions like 'fcntl' In-Reply-To: References: Message-ID: Thank you for the explanation, Armin. It's as I thought. OK, then a brief announcement for potential sandbox champions on this list :) Our early-stage startup (Grist Labs ) is looking for an engineer who can also be a pypy sandbox champion! Competitive salary, benefits, equity, plus the ability (and encouragement) to contribute to pypy. For the moment, we are only offering a full-time position in New York City, but if you have a strong interest elsewhere, let's talk anyway. I hope this isn't an abuse of this list, but really: the pypy sandbox is an important and promising tools for us. We'd like to contribute what we can. Dmitry On Tue, Jun 9, 2015 at 2:46 AM, Armin Rigo wrote: > Hi Dmitry, > > On 9 June 2015 at 05:10, Dmitry Sagalovskiy wrote: > > More generally, my team needs to decide if we can rely on the pypy > sandbox to use in our product. It seems brilliantly designed, fast, and > overall impressive. But there are these gaps in missing sandbox wrappers > (there are others too, fcntl is just one that I don't know how to avoid). > And I noticed some code that indicates that it is not supported on Windows > -- is that the case? > > What are the sandbox's prospects, within the larger future of pypy? > > The sandbox code is there and "mostly working", but it is lacking a > champion. It has been in this state for many years now (it is > actually impressive that it still roughly works). Realistically, > though, to answer the question of its prospects, it depends entirely > on whether someone would be ready to become involved in PyPy and help > maintain and develop it. As usual with Open Source, we can't predict > when (and if) this will occur. From our point of view, it seems to > attract occasional attention like yours, but we just have too many > things to work on. > > > If anyone can suggest what I might be doing wrong, I would greatly > > appreciate. > > You're not doing anything wrong, just stumbling on a mixture of old > and new code. In the case of 'pypy_jit_depthmap_add', it's because we > recently added vmprof support and didn't think about sandboxing. The > fix is probably easy: we need a few "sandboxsafe=True" keyword > arguments in rpython/jit/backend/llsupport/codemap.py. The issue with > 'fcntl' is more obscure and involves much older code. In that case we > need the sandboxed interpreter to ask the outside what to do---which > should occur automatically, but doesn't, for reasons I'm still > investigating. I suspect it's related to the XXX in the comment of > select_function_code_generators() in rpython.translator.c.node. (I > think with minimal effort we can finally get rid of the "oldstyle" > functions mentioned there.) > > > A bient?t, > > Armin. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at manueljacob.de Tue Jun 9 18:09:48 2015 From: me at manueljacob.de (Manuel Jacob) Date: Tue, 09 Jun 2015 18:09:48 +0200 Subject: [pypy-dev] py3k and py3.3 branches In-Reply-To: References: Message-ID: <885c514a8344fa58327eb53d64fc45f3@indus.uberspace.de> Hi Ludovic, please excuse the late answer. On 2015-06-06 08:09, Ludovic Gasc wrote: > I see more activity on py3k than py3.3. > What the branch you recommend to test Python3 support of PyPy ? py3k ? > > The next stable release of PyPy3 will be based on py3.3 ? The py3k branch contains a stable and almost complete implementation of Python 3.2, while the the py3.3 branch contains an experimental and incomplete implementation of Python 3.3. The next stable release of PyPy3, which is planned to be released this week, will be based on the (stable) py3k branch. This is also the reason why you currently see more activity on the py3k branch. -Manuel From ram at rachum.com Tue Jun 9 18:58:37 2015 From: ram at rachum.com (Ram Rachum) Date: Tue, 9 Jun 2015 19:58:37 +0300 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 Message-ID: Hi everyone, I want to test my PyPI package on pypy3, but my package only support Python 3.3 and above. I know that a version of pypy3 that support Python 3.3 is not ready yet, but is there a development version of it that I can run so I could test my package and find any bugs in it? (And possibly also bugs in pypy.) Thanks, Ram. -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Tue Jun 9 19:02:44 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Tue, 9 Jun 2015 19:02:44 +0200 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: 2015-06-09 18:58 GMT+02:00 Ram Rachum : > Hi everyone, > > I want to test my PyPI package on pypy3, but my package only support > Python 3.3 and above. I know that a version of pypy3 that support Python > 3.3 is not ready yet, but is there a development version of it that I can > run so I could test my package and find any bugs in it? (And possibly also > bugs in pypy.) > Sure, we have builds for the linux64 platform: http://buildbot.pypy.org/nightly/py3.3/ -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Tue Jun 9 19:03:58 2015 From: ram at rachum.com (Ram Rachum) Date: Tue, 9 Jun 2015 20:03:58 +0300 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: Ah... Can I get that in Windows please? On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc wrote: > 2015-06-09 18:58 GMT+02:00 Ram Rachum : > >> Hi everyone, >> >> I want to test my PyPI package on pypy3, but my package only support >> Python 3.3 and above. I know that a version of pypy3 that support Python >> 3.3 is not ready yet, but is there a development version of it that I can >> run so I could test my package and find any bugs in it? (And possibly also >> bugs in pypy.) >> > > Sure, we have builds for the linux64 platform: > http://buildbot.pypy.org/nightly/py3.3/ > > > -- > Amaury Forgeot d'Arc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Tue Jun 9 19:11:12 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Tue, 9 Jun 2015 19:11:12 +0200 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: 2015-06-09 19:03 GMT+02:00 Ram Rachum : > Ah... Can I get that in Windows please? > I just started a translation. Please be patient, and it's very possible that it breaks in the middle... > > On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc > wrote: > >> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >> >>> Hi everyone, >>> >>> I want to test my PyPI package on pypy3, but my package only support >>> Python 3.3 and above. I know that a version of pypy3 that support Python >>> 3.3 is not ready yet, but is there a development version of it that I can >>> run so I could test my package and find any bugs in it? (And possibly also >>> bugs in pypy.) >>> >> >> Sure, we have builds for the linux64 platform: >> http://buildbot.pypy.org/nightly/py3.3/ >> >> >> -- >> Amaury Forgeot d'Arc >> > > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Tue Jun 9 19:15:01 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Tue, 9 Jun 2015 19:15:01 +0200 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: 2015-06-09 19:11 GMT+02:00 Amaury Forgeot d'Arc : > 2015-06-09 19:03 GMT+02:00 Ram Rachum : > >> Ah... Can I get that in Windows please? >> > > I just started a translation. > Please be patient, and it's very possible that it breaks in the middle... > Actually it broke at the beginning :-/ http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/1921/steps/translate/logs/stdio [translation:info] File "c:\pypy\buildbot\pypy-c-jit-win-x86-32\build\rpython\rlib\rposix.py", line 273, in replace [translation:info] 'On windows, os.replace() should overwrite the destination') [translation:ERROR] NotImplementedError: On windows, os.replace() should overwrite the destination > > >> >> On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc >> wrote: >> >>> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >>> >>>> Hi everyone, >>>> >>>> I want to test my PyPI package on pypy3, but my package only support >>>> Python 3.3 and above. I know that a version of pypy3 that support Python >>>> 3.3 is not ready yet, but is there a development version of it that I can >>>> run so I could test my package and find any bugs in it? (And possibly also >>>> bugs in pypy.) >>>> >>> >>> Sure, we have builds for the linux64 platform: >>> http://buildbot.pypy.org/nightly/py3.3/ >>> >>> >>> -- >>> Amaury Forgeot d'Arc >>> >> >> > > > -- > Amaury Forgeot d'Arc > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Tue Jun 9 20:01:43 2015 From: ram at rachum.com (Ram Rachum) Date: Tue, 9 Jun 2015 21:01:43 +0300 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: Ah, so I guess I have no choice but to download the linux version. I never downloaded Linux software before (only installed with package managers). How do you do that? Is it just a folder you download and run or is there some extra process involved? On Tue, Jun 9, 2015 at 8:15 PM, Amaury Forgeot d'Arc wrote: > 2015-06-09 19:11 GMT+02:00 Amaury Forgeot d'Arc : > >> 2015-06-09 19:03 GMT+02:00 Ram Rachum : >> >>> Ah... Can I get that in Windows please? >>> >> >> I just started a translation. >> Please be patient, and it's very possible that it breaks in the middle... >> > > Actually it broke at the beginning :-/ > > > http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/1921/steps/translate/logs/stdio > [translation:info] File > "c:\pypy\buildbot\pypy-c-jit-win-x86-32\build\rpython\rlib\rposix.py", line > 273, in replace > [translation:info] 'On windows, os.replace() should overwrite the > destination') > [translation:ERROR] NotImplementedError: On windows, os.replace() should > overwrite the destination > > > >> >> >>> >>> On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc >> > wrote: >>> >>>> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >>>> >>>>> Hi everyone, >>>>> >>>>> I want to test my PyPI package on pypy3, but my package only support >>>>> Python 3.3 and above. I know that a version of pypy3 that support Python >>>>> 3.3 is not ready yet, but is there a development version of it that I can >>>>> run so I could test my package and find any bugs in it? (And possibly also >>>>> bugs in pypy.) >>>>> >>>> >>>> Sure, we have builds for the linux64 platform: >>>> http://buildbot.pypy.org/nightly/py3.3/ >>>> >>>> >>>> -- >>>> Amaury Forgeot d'Arc >>>> >>> >>> >> >> >> -- >> Amaury Forgeot d'Arc >> > > > > -- > Amaury Forgeot d'Arc > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Tue Jun 9 20:19:07 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Tue, 9 Jun 2015 13:19:07 -0500 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: :: curl -L http://buildbot.pypy.org/nightly/py3.3/pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 > pypy.tar.bz2 tar xf pypy.tar.bz2 cd pypy-c-jit* cd bin ./pypy # or ./pypy-c? I *think* this is what you'd need to run. On Tue, Jun 9, 2015 at 1:01 PM, Ram Rachum wrote: > Ah, so I guess I have no choice but to download the linux version. I never > downloaded Linux software before (only installed with package managers). > How do you do that? Is it just a folder you download and run or is there > some extra process involved? > > On Tue, Jun 9, 2015 at 8:15 PM, Amaury Forgeot d'Arc > wrote: > >> 2015-06-09 19:11 GMT+02:00 Amaury Forgeot d'Arc : >> >>> 2015-06-09 19:03 GMT+02:00 Ram Rachum : >>> >>>> Ah... Can I get that in Windows please? >>>> >>> >>> I just started a translation. >>> Please be patient, and it's very possible that it breaks in the middle... >>> >> >> Actually it broke at the beginning :-/ >> >> >> http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/1921/steps/translate/logs/stdio >> [translation:info] File >> "c:\pypy\buildbot\pypy-c-jit-win-x86-32\build\rpython\rlib\rposix.py", line >> 273, in replace >> [translation:info] 'On windows, os.replace() should overwrite the >> destination') >> [translation:ERROR] NotImplementedError: On windows, os.replace() should >> overwrite the destination >> >> >> >>> >>> >>>> >>>> On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc < >>>> amauryfa at gmail.com> wrote: >>>> >>>>> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> I want to test my PyPI package on pypy3, but my package only support >>>>>> Python 3.3 and above. I know that a version of pypy3 that support Python >>>>>> 3.3 is not ready yet, but is there a development version of it that I can >>>>>> run so I could test my package and find any bugs in it? (And possibly also >>>>>> bugs in pypy.) >>>>>> >>>>> >>>>> Sure, we have builds for the linux64 platform: >>>>> http://buildbot.pypy.org/nightly/py3.3/ >>>>> >>>>> >>>>> -- >>>>> Amaury Forgeot d'Arc >>>>> >>>> >>>> >>> >>> >>> -- >>> Amaury Forgeot d'Arc >>> >> >> >> >> -- >> Amaury Forgeot d'Arc >> > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something?s wrong. http://kirbyfan64.github.io/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Tue Jun 9 20:44:17 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Tue, 9 Jun 2015 20:44:17 +0200 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: 2015-06-09 20:01 GMT+02:00 Ram Rachum : > Ah, so I guess I have no choice but to download the linux version. I never > downloaded Linux software before (only installed with package managers). > How do you do that? Is it just a folder you download and run or is there > some extra process involved? > Just unpack the archive in any directory, and run pypy from there. http://pypy.org/download.html#installing I usually use a command like: tar xvaf /path/to/pypy-c.tar.bz2 . > > On Tue, Jun 9, 2015 at 8:15 PM, Amaury Forgeot d'Arc > wrote: > >> 2015-06-09 19:11 GMT+02:00 Amaury Forgeot d'Arc : >> >>> 2015-06-09 19:03 GMT+02:00 Ram Rachum : >>> >>>> Ah... Can I get that in Windows please? >>>> >>> >>> I just started a translation. >>> Please be patient, and it's very possible that it breaks in the middle... >>> >> >> Actually it broke at the beginning :-/ >> >> >> http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/1921/steps/translate/logs/stdio >> [translation:info] File >> "c:\pypy\buildbot\pypy-c-jit-win-x86-32\build\rpython\rlib\rposix.py", line >> 273, in replace >> [translation:info] 'On windows, os.replace() should overwrite the >> destination') >> [translation:ERROR] NotImplementedError: On windows, os.replace() should >> overwrite the destination >> >> >> >>> >>> >>>> >>>> On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc < >>>> amauryfa at gmail.com> wrote: >>>> >>>>> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >>>>> >>>>>> Hi everyone, >>>>>> >>>>>> I want to test my PyPI package on pypy3, but my package only support >>>>>> Python 3.3 and above. I know that a version of pypy3 that support Python >>>>>> 3.3 is not ready yet, but is there a development version of it that I can >>>>>> run so I could test my package and find any bugs in it? (And possibly also >>>>>> bugs in pypy.) >>>>>> >>>>> >>>>> Sure, we have builds for the linux64 platform: >>>>> http://buildbot.pypy.org/nightly/py3.3/ >>>>> >>>>> >>>>> -- >>>>> Amaury Forgeot d'Arc >>>>> >>>> >>>> >>> >>> >>> -- >>> Amaury Forgeot d'Arc >>> >> >> >> >> -- >> Amaury Forgeot d'Arc >> > > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From gmludo at gmail.com Tue Jun 9 21:43:26 2015 From: gmludo at gmail.com (Ludovic Gasc) Date: Tue, 9 Jun 2015 21:43:26 +0200 Subject: [pypy-dev] py3k and py3.3 branches In-Reply-To: <885c514a8344fa58327eb53d64fc45f3@indus.uberspace.de> References: <885c514a8344fa58327eb53d64fc45f3@indus.uberspace.de> Message-ID: Don't worry about delay, I know it's a best effort support mode, like me ;-) Thanks for your answer, it's more clear to me. Ludovic Gasc (GMLudo) http://www.gmludo.eu/ On 9 Jun 2015 18:09, "Manuel Jacob" wrote: > Hi Ludovic, > > please excuse the late answer. > > On 2015-06-06 08:09, Ludovic Gasc wrote: > >> I see more activity on py3k than py3.3. >> What the branch you recommend to test Python3 support of PyPy ? py3k ? >> >> The next stable release of PyPy3 will be based on py3.3 ? >> > > The py3k branch contains a stable and almost complete implementation of > Python 3.2, while the the py3.3 branch contains an experimental and > incomplete implementation of Python 3.3. The next stable release of PyPy3, > which is planned to be released this week, will be based on the (stable) > py3k branch. This is also the reason why you currently see more activity > on the py3k branch. > > -Manuel > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Wed Jun 10 20:53:49 2015 From: ram at rachum.com (Ram Rachum) Date: Wed, 10 Jun 2015 21:53:49 +0300 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: I tried it, got this error: debug: OperationError: debug: operror-type: ImportError debug: operror-value: No module named 'encodings' debug: OperationError: debug: operror-type: AttributeError debug: operror-value: stdout On Tue, Jun 9, 2015 at 9:19 PM, Ryan Gonzalez wrote: > :: > > curl -L > http://buildbot.pypy.org/nightly/py3.3/pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 > > pypy.tar.bz2 > tar xf pypy.tar.bz2 > cd pypy-c-jit* > cd bin > ./pypy # or ./pypy-c? > > I *think* this is what you'd need to run. > > > On Tue, Jun 9, 2015 at 1:01 PM, Ram Rachum wrote: > >> Ah, so I guess I have no choice but to download the linux version. I >> never downloaded Linux software before (only installed with package >> managers). How do you do that? Is it just a folder you download and run or >> is there some extra process involved? >> >> On Tue, Jun 9, 2015 at 8:15 PM, Amaury Forgeot d'Arc >> wrote: >> >>> 2015-06-09 19:11 GMT+02:00 Amaury Forgeot d'Arc : >>> >>>> 2015-06-09 19:03 GMT+02:00 Ram Rachum : >>>> >>>>> Ah... Can I get that in Windows please? >>>>> >>>> >>>> I just started a translation. >>>> Please be patient, and it's very possible that it breaks in the >>>> middle... >>>> >>> >>> Actually it broke at the beginning :-/ >>> >>> >>> http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/1921/steps/translate/logs/stdio >>> [translation:info] File >>> "c:\pypy\buildbot\pypy-c-jit-win-x86-32\build\rpython\rlib\rposix.py", line >>> 273, in replace >>> [translation:info] 'On windows, os.replace() should overwrite the >>> destination') >>> [translation:ERROR] NotImplementedError: On windows, os.replace() should >>> overwrite the destination >>> >>> >>> >>>> >>>> >>>>> >>>>> On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc < >>>>> amauryfa at gmail.com> wrote: >>>>> >>>>>> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >>>>>> >>>>>>> Hi everyone, >>>>>>> >>>>>>> I want to test my PyPI package on pypy3, but my package only support >>>>>>> Python 3.3 and above. I know that a version of pypy3 that support Python >>>>>>> 3.3 is not ready yet, but is there a development version of it that I can >>>>>>> run so I could test my package and find any bugs in it? (And possibly also >>>>>>> bugs in pypy.) >>>>>>> >>>>>> >>>>>> Sure, we have builds for the linux64 platform: >>>>>> http://buildbot.pypy.org/nightly/py3.3/ >>>>>> >>>>>> >>>>>> -- >>>>>> Amaury Forgeot d'Arc >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Amaury Forgeot d'Arc >>>> >>> >>> >>> >>> -- >>> Amaury Forgeot d'Arc >>> >> >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> >> > > > -- > Ryan > [ERROR]: Your autotools build scripts are 200 lines longer than your > program. Something?s wrong. > http://kirbyfan64.github.io/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengha.mao at gmail.com Thu Jun 11 05:30:37 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Thu, 11 Jun 2015 11:30:37 +0800 Subject: [pypy-dev] Could we set working dir of pypy_execute_source_ptr()? Message-ID: Here is a typcial scenario: We read a python file from a path and got (char*) buffer of the file content. And then we passed the char* buffer to pypy_execute_source_ptr() to execute. However, pypy_execute_source_ptr() looks like to assume the working dir as pypy_home. And if the python file import a local file in the path, it failed. Alternative method, could we have a pypy_execute_source_ptr(path pyFile, void *ptr)? The first argument indicates the path of python file. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fijall at gmail.com Thu Jun 11 09:10:11 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Thu, 11 Jun 2015 09:10:11 +0200 Subject: [pypy-dev] Could we set working dir of pypy_execute_source_ptr()? In-Reply-To: References: Message-ID: you can do arbitrary stuff in the python code, including "import sys; sys.path.insert(0, 'wherever')" On Thu, Jun 11, 2015 at 5:30 AM, Yicong Huang wrote: > Here is a typcial scenario: > We read a python file from a path and got (char*) buffer of the file > content. > And then we passed the char* buffer to pypy_execute_source_ptr() to execute. > However, pypy_execute_source_ptr() looks like to assume the working dir as > pypy_home. > And if the python file import a local file in the path, it failed. > > Alternative method, could we have a pypy_execute_source_ptr(path pyFile, > void *ptr)? The first argument indicates the path of python file. > > > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > From ram at rachum.com Thu Jun 11 14:54:05 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 15:54:05 +0300 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: Can someone please help? I want to get Pypy running and I don't know how. On Wed, Jun 10, 2015 at 9:53 PM, Ram Rachum wrote: > I tried it, got this error: > > debug: OperationError: > debug: operror-type: ImportError > debug: operror-value: No module named 'encodings' > debug: OperationError: > debug: operror-type: AttributeError > debug: operror-value: stdout > > > On Tue, Jun 9, 2015 at 9:19 PM, Ryan Gonzalez wrote: > >> :: >> >> curl -L >> http://buildbot.pypy.org/nightly/py3.3/pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 >> > pypy.tar.bz2 >> tar xf pypy.tar.bz2 >> cd pypy-c-jit* >> cd bin >> ./pypy # or ./pypy-c? >> >> I *think* this is what you'd need to run. >> >> >> On Tue, Jun 9, 2015 at 1:01 PM, Ram Rachum wrote: >> >>> Ah, so I guess I have no choice but to download the linux version. I >>> never downloaded Linux software before (only installed with package >>> managers). How do you do that? Is it just a folder you download and run or >>> is there some extra process involved? >>> >>> On Tue, Jun 9, 2015 at 8:15 PM, Amaury Forgeot d'Arc >> > wrote: >>> >>>> 2015-06-09 19:11 GMT+02:00 Amaury Forgeot d'Arc : >>>> >>>>> 2015-06-09 19:03 GMT+02:00 Ram Rachum : >>>>> >>>>>> Ah... Can I get that in Windows please? >>>>>> >>>>> >>>>> I just started a translation. >>>>> Please be patient, and it's very possible that it breaks in the >>>>> middle... >>>>> >>>> >>>> Actually it broke at the beginning :-/ >>>> >>>> >>>> http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/1921/steps/translate/logs/stdio >>>> [translation:info] File >>>> "c:\pypy\buildbot\pypy-c-jit-win-x86-32\build\rpython\rlib\rposix.py", line >>>> 273, in replace >>>> [translation:info] 'On windows, os.replace() should overwrite the >>>> destination') >>>> [translation:ERROR] NotImplementedError: On windows, os.replace() >>>> should overwrite the destination >>>> >>>> >>>> >>>>> >>>>> >>>>>> >>>>>> On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc < >>>>>> amauryfa at gmail.com> wrote: >>>>>> >>>>>>> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >>>>>>> >>>>>>>> Hi everyone, >>>>>>>> >>>>>>>> I want to test my PyPI package on pypy3, but my package only >>>>>>>> support Python 3.3 and above. I know that a version of pypy3 that support >>>>>>>> Python 3.3 is not ready yet, but is there a development version of it that >>>>>>>> I can run so I could test my package and find any bugs in it? (And possibly >>>>>>>> also bugs in pypy.) >>>>>>>> >>>>>>> >>>>>>> Sure, we have builds for the linux64 platform: >>>>>>> http://buildbot.pypy.org/nightly/py3.3/ >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Amaury Forgeot d'Arc >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Amaury Forgeot d'Arc >>>>> >>>> >>>> >>>> >>>> -- >>>> Amaury Forgeot d'Arc >>>> >>> >>> >>> _______________________________________________ >>> pypy-dev mailing list >>> pypy-dev at python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >>> >>> >> >> >> -- >> Ryan >> [ERROR]: Your autotools build scripts are 200 lines longer than your >> program. Something?s wrong. >> http://kirbyfan64.github.io/ >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 16:27:12 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 17:27:12 +0300 Subject: [pypy-dev] Question Message-ID: When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , how do I access the pip that belongs to PyPy? -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 16:28:37 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 17:28:37 +0300 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> References: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> Message-ID: Didn't work. On Thu, Jun 11, 2015 at 5:21 PM, Ryan Gonzalez wrote: > Random (probably wrong) idea: setting PYTHONPATH to ../lib-pypy (I think?). > > On June 11, 2015 7:54:05 AM CDT, Ram Rachum wrote: >> >> Can someone please help? I want to get Pypy running and I don't know how. >> >> On Wed, Jun 10, 2015 at 9:53 PM, Ram Rachum wrote: >> >>> I tried it, got this error: >>> >>> debug: OperationError: >>> debug: operror-type: ImportError >>> debug: operror-value: No module named 'encodings' >>> debug: OperationError: >>> debug: operror-type: AttributeError >>> debug: operror-value: stdout >>> >>> >>> On Tue, Jun 9, 2015 at 9:19 P M, Ryan Gonzalez wrote: >>> >>>> :: >>>> >>>> curl -L >>>> http://buildbot.pypy.org/nightly/py3.3/pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 >>>> > pypy.tar.bz2 >>>> tar xf pypy.tar.bz2 >>>> cd pypy-c-jit* >>>> cd bin >>>> ./pypy # or ./pypy-c? >>>> >>>> I *think* this is what you'd need to run. >>>> >>>> >>>> On Tue, Jun 9, 2015 at 1:01 PM, Ram Rachum wrote: >>>> >>>>> Ah, so I guess I have no choice but to download the linux version. I >>>>> never downloaded Linux software before (only installed with package >>>>> managers). How do you do that? Is it just a folder you download and run or >>>>> is there some extra process involved? >>>>> >>>>> On Tue, Jun 9, 2015 at 8:15 PM, Amaury Forgeot d'Arc < >>>>> amauryfa at gmail.com> wrote: >>>>> >>>>>> 2015-06-09 19:11 GMT+02:00 Amaury Forgeot d'Arc : >>>>>> >>>>>>> 2015-06-09 19:03 GMT+02:00 Ram Rachum : >>>>>>> >>>>>>>> Ah... Can I get that in Windows please? >>>>>>>> >>>>>>> >>>>>>> I just started a translation. >>>>>>> Please be patient, and it's very possible that it breaks in the >>>>>>> middle... >>>>>>> >>>>>> >>>>>> Actually it broke at the beginning :-/ >>>>>> >>>>>> >>>>>> http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/1921/steps/translate/logs/stdio >>>>>> [translation:info] File >>>>>> "c:\pypy\buildbot\pypy-c-jit-win-x86-32\build\rpython\rlib\rposix.py", line >>>>>> 273, in replace >>>>>> [translation:info] 'On windows, os.replace() should overwrite the >>>>>> destination') >>>>>> [translation:ERROR] NotImplementedError: On windows, os.replace() >>>>>> should overwrite the destination >>>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc < >>>>>>>> amauryfa at gmail.com> wrote: >>>>>>>> >>>>>>>>> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >>>>>>>>> >>>>>>>>>> Hi everyone, >>>>>>>>>> >>>>>>>>>> I want to test my PyPI package on pypy3, but my package only >>>>>>>>>> support Python 3.3 and above. I know that a version of pypy3 that support >>>>>>>>>> Python 3.3 is not ready yet, but is there a development version of it th at >>>>>>>>>> I can run so I could test my package and find any bugs in it? (And possibly >>>>>>>>>> also bugs in pypy.) >>>>>>>>>> >>>>>>>>> >>>>>>>>> Sure, we have builds for the linux64 platform: >>>>>>>>> http://buildbot.pypy.org/nightly/py3.3/ >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Amaury Forgeot d'Arc >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Amaury Forgeot d'Arc >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Amaury Forgeot d'Arc >>>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> pypy-dev mailing list >>>>> pypy-dev at python.org >>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Ryan >>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>> program. Something?s wrong. >>>> http://kirbyfan64.github.io/ >>>> >>>> >>> >>> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Thu Jun 11 16:21:39 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 09:21:39 -0500 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: Message-ID: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> Random (probably wrong) idea: setting PYTHONPATH to ../lib-pypy (I think?). On June 11, 2015 7:54:05 AM CDT, Ram Rachum wrote: >Can someone please help? I want to get Pypy running and I don't know >how. > >On Wed, Jun 10, 2015 at 9:53 PM, Ram Rachum wrote: > >> I tried it, got this error: >> >> debug: OperationError: >> debug: operror-type: ImportError >> debug: operror-value: No module named 'encodings' >> debug: OperationError: >> debug: operror-type: AttributeError >> debug: operror-value: stdout >> >> >> On Tue, Jun 9, 2015 at 9:19 PM, Ryan Gonzalez >wrote: >> >>> :: >>> >>> curl -L >>> >http://buildbot.pypy.org/nightly/py3.3/pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 >>> > pypy.tar.bz2 >>> tar xf pypy.tar.bz2 >>> cd pypy-c-jit* >>> cd bin >>> ./pypy # or ./pypy-c? >>> >>> I *think* this is what you'd need to run. >>> >>> >>> On Tue, Jun 9, 2015 at 1:01 PM, Ram Rachum wrote: >>> >>>> Ah, so I guess I have no choice but to download the linux version. >I >>>> never downloaded Linux software before (only installed with package >>>> managers). How do you do that? Is it just a folder you download and >run or >>>> is there some extra process involved? >>>> >>>> On Tue, Jun 9, 2015 at 8:15 PM, Amaury Forgeot d'Arc >>>> > wrote: >>>> >>>>> 2015-06-09 19:11 GMT+02:00 Amaury Forgeot d'Arc >: >>>>> >>>>>> 2015-06-09 19:03 GMT+02:00 Ram Rachum : >>>>>> >>>>>>> Ah... Can I get that in Windows please? >>>>>>> >>>>>> >>>>>> I just started a translation. >>>>>> Please be patient, and it's very possible that it breaks in the >>>>>> middle... >>>>>> >>>>> >>>>> Actually it broke at the beginning :-/ >>>>> >>>>> >>>>> >http://buildbot.pypy.org/builders/pypy-c-jit-win-x86-32/builds/1921/steps/translate/logs/stdio >>>>> [translation:info] File >>>>> >"c:\pypy\buildbot\pypy-c-jit-win-x86-32\build\rpython\rlib\rposix.py", >line >>>>> 273, in replace >>>>> [translation:info] 'On windows, os.replace() should overwrite >the >>>>> destination') >>>>> [translation:ERROR] NotImplementedError: On windows, os.replace() >>>>> should overwrite the destination >>>>> >>>>> >>>>> >>>>>> >>>>>> >>>>>>> >>>>>>> On Tue, Jun 9, 2015 at 8:02 PM, Amaury Forgeot d'Arc < >>>>>>> amauryfa at gmail.com> wrote: >>>>>>> >>>>>>>> 2015-06-09 18:58 GMT+02:00 Ram Rachum : >>>>>>>> >>>>>>>>> Hi everyone, >>>>>>>>> >>>>>>>>> I want to test my PyPI package on pypy3, but my package only >>>>>>>>> support Python 3.3 and above. I know that a version of pypy3 >that support >>>>>>>>> Python 3.3 is not ready yet, but is there a development >version of it that >>>>>>>>> I can run so I could test my package and find any bugs in it? >(And possibly >>>>>>>>> also bugs in pypy.) >>>>>>>>> >>>>>>>> >>>>>>>> Sure, we have builds for the linux64 platform: >>>>>>>> http://buildbot.pypy.org/nightly/py3.3/ >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Amaury Forgeot d'Arc >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Amaury Forgeot d'Arc >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Amaury Forgeot d'Arc >>>>> >>>> >>>> >>>> _______________________________________________ >>>> pypy-dev mailing list >>>> pypy-dev at python.org >>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>> >>>> >>> >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something?s wrong. >>> http://kirbyfan64.github.io/ >>> >>> >> >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Thu Jun 11 16:36:11 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 09:36:11 -0500 Subject: [pypy-dev] Question In-Reply-To: References: Message-ID: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , >how >do I access the pip that belongs to PyPy? > > >------------------------------------------------------------------------ > >_______________________________________________ >pypy-dev mailing list >pypy-dev at python.org >https://mail.python.org/mailman/listinfo/pypy-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 16:46:05 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 17:46:05 +0300 Subject: [pypy-dev] Question In-Reply-To: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> Message-ID: Things I don't care about so much right now: - How fast PyPy runs. Things I care *a lot* about right now: - How many hours of my life I need to spend to get PyPy to run. On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez wrote: > Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. > > > On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >> >> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , >> how do I access the pip that belongs to PyPy? >> >> ------------------------------ >> >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fijall at gmail.com Thu Jun 11 16:48:16 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Thu, 11 Jun 2015 16:48:16 +0200 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> Message-ID: you can install pypy with apt-get. Stuff gets installed in site-packages I believe (just like on cpython) On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: > Things I don't care about so much right now: > - How fast PyPy runs. > > Things I care a lot about right now: > - How many hours of my life I need to spend to get PyPy to run. > > On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez wrote: >> >> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >> >> >> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>> >>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , >>> how do I access the pip that belongs to PyPy? >>> >>> ________________________________ >>> >>> pypy-dev mailing list >>> pypy-dev at python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >> >> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > From ram at rachum.com Thu Jun 11 17:00:50 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 18:00:50 +0300 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> Message-ID: As far as I know scripts don't get installed to site packages (at least on windows). In other words: say I installed pypy on Ubuntu with nose in it. I want to launch the nosetests script. (I also have one for the system Python.) How do I launch the nosetests that belongs to PyPy? On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: > you can install pypy with apt-get. Stuff gets installed in > site-packages I believe (just like on cpython) > > On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: > > Things I don't care about so much right now: > > - How fast PyPy runs. > > > > Things I care a lot about right now: > > - How many hours of my life I need to spend to get PyPy to run. > > > > On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez wrote: > >> > >> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. > >> > >> > >> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: > >>> > >>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , > >>> how do I access the pip that belongs to PyPy? > >>> > >>> ________________________________ > >>> > >>> pypy-dev mailing list > >>> pypy-dev at python.org > >>> https://mail.python.org/mailman/listinfo/pypy-dev > >> > >> > >> -- > >> Sent from my Android device with K-9 Mail. Please excuse my brevity. > > > > > > > > _______________________________________________ > > pypy-dev mailing list > > pypy-dev at python.org > > https://mail.python.org/mailman/listinfo/pypy-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wizzat at gmail.com Thu Jun 11 17:02:49 2015 From: wizzat at gmail.com (Mark Roberts) Date: Thu, 11 Jun 2015 08:02:49 -0700 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> Message-ID: I've had the best luck with Pyenv. -Mark > On Jun 11, 2015, at 07:46, Ram Rachum wrote: > > Things I don't care about so much right now: > - How fast PyPy runs. > > Things I care a lot about right now: > - How many hours of my life I need to spend to get PyPy to run. > >> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez wrote: >> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >> >> >>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , how do I access the pip that belongs to PyPy? >>> >>> pypy-dev mailing list >>> pypy-dev at python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: From fijall at gmail.com Thu Jun 11 17:26:55 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Thu, 11 Jun 2015 17:26:55 +0200 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> Message-ID: if you just unpack pypy, the packages get installed in bin/ or site-packages/ that belongs there. How ubuntu does it I have no clue. I would use virtualenv On Thu, Jun 11, 2015 at 5:00 PM, Ram Rachum wrote: > As far as I know scripts don't get installed to site packages (at least on > windows). > > In other words: say I installed pypy on Ubuntu with nose in it. I want to > launch the nosetests script. (I also have one for the system Python.) How do > I launch the nosetests that belongs to PyPy? > > On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >> >> you can install pypy with apt-get. Stuff gets installed in >> site-packages I believe (just like on cpython) >> >> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >> > Things I don't care about so much right now: >> > - How fast PyPy runs. >> > >> > Things I care a lot about right now: >> > - How many hours of my life I need to spend to get PyPy to run. >> > >> > On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez wrote: >> >> >> >> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >> >> >> >> >> >> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >> >>> >> >>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , >> >>> how do I access the pip that belongs to PyPy? >> >>> >> >>> ________________________________ >> >>> >> >>> pypy-dev mailing list >> >>> pypy-dev at python.org >> >>> https://mail.python.org/mailman/listinfo/pypy-dev >> >> >> >> >> >> -- >> >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> > >> > >> > >> > _______________________________________________ >> > pypy-dev mailing list >> > pypy-dev at python.org >> > https://mail.python.org/mailman/listinfo/pypy-dev >> > From rymg19 at gmail.com Thu Jun 11 18:05:31 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 11:05:31 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> Message-ID: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> I don't think you can out-of-the-box without some env tool. Blame apt-get's brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY DON'T WORK! [which is probably why Torvalds never distributes app binaries for Linux]), I do things the simple way: build it myself. Takes about 45 mins. Always works. pip and pytest and such will all get installed into the source directory/bin, NOT /usr/local. In order to access them easily, I put something like this in my .bashrc: for bin in $STUFF/pypy/bin; do alias pypy-${bin##*/}=$bin done # Laziness alias pypy="$STUFF/pypy/pypy-c" # it was either that or: alias pypy="$STUFF/pypy/bin/pypy-c" On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >As far as I know scripts don't get installed to site packages (at least >on >windows). > >In other words: say I installed pypy on Ubuntu with nose in it. I want >to >launch the nosetests script. (I also have one for the system Python.) >How >do I launch the nosetests that belongs to PyPy? >On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: > >> you can install pypy with apt-get. Stuff gets installed in >> site-packages I believe (just like on cpython) >> >> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >> > Things I don't care about so much right now: >> > - How fast PyPy runs. >> > >> > Things I care a lot about right now: >> > - How many hours of my life I need to spend to get PyPy to run. >> > >> > On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >wrote: >> >> >> >> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >> >> >> >> >> >> On June 11, 2015 9:27:12 AM CDT, Ram Rachum >wrote: >> >>> >> >>> When I install Pypy on Ubuntu using apt-get, and then run >get-pip.py , >> >>> how do I access the pip that belongs to PyPy? >> >>> >> >>> ________________________________ >> >>> >> >>> pypy-dev mailing list >> >>> pypy-dev at python.org >> >>> https://mail.python.org/mailman/listinfo/pypy-dev >> >> >> >> >> >> -- >> >> Sent from my Android device with K-9 Mail. Please excuse my >brevity. >> > >> > >> > >> > _______________________________________________ >> > pypy-dev mailing list >> > pypy-dev at python.org >> > https://mail.python.org/mailman/listinfo/pypy-dev >> > >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From romain.py at gmail.com Thu Jun 11 18:44:38 2015 From: romain.py at gmail.com (Romain Guillebert) Date: Thu, 11 Jun 2015 17:44:38 +0100 Subject: [pypy-dev] Question In-Reply-To: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> Message-ID: pypy -m pip works On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: > I don't think you can out-of-the-box without some env tool. Blame apt-get's > brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY > DON'T WORK! [which is probably why Torvalds never distributes app binaries > for Linux]), I do things the simple way: build it myself. Takes about 45 > mins. Always works. pip and pytest and such will all get installed into the > source directory/bin, NOT /usr/local. In order to access them easily, I put > something like this in my .bashrc: > > for bin in $STUFF/pypy/bin; do > alias pypy-${bin##*/}=$bin > done > > # Laziness > alias pypy="$STUFF/pypy/pypy-c" > # it was either that or: > alias pypy="$STUFF/pypy/bin/pypy-c" > > > > On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >> >> As far as I know scripts don't get installed to site packages (at least on >> windows). >> >> In other words: say I installed pypy on Ubuntu with nose in it. I want to >> launch the nosetests script. (I also have one for the system Python.) How do >> I launch the nosetests that belongs to PyPy? >> >> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>> >>> you can install pypy with apt-get. Stuff gets installed in >>> site-packages I believe (just like on cpython) >>> >>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>> > Things I don't care about so much right now: >>> > - How fast PyPy runs. >>> > >>> > Things I care a lot about right now: >>> > - How many hours of my life I need to spend to get PyPy to run. >>> > >>> > On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>> > wrote: >>> >> >>> >> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>> >> >>> >> >>> >> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>> >>> >>> >>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>> >>> , >>> >>> how do I access the pip that belongs to PyPy? >>> >>> >>> >>> ________________________________ >>> >>> >>> >>> pypy-dev mailing list >>> >>> pypy-dev at python.org >>> >>> https://mail.python.org/mailman/listinfo/pypy-dev >>> >> >>> >> >>> >> -- >>> >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>> > >>> > >>> > >>> > _______________________________________________ >>> > pypy-dev mailing list >>> > pypy-dev at python.org >>> > https://mail.python.org/mailman/listinfo/pypy-dev >>> > > > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > From rymg19 at gmail.com Thu Jun 11 19:15:48 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 12:15:48 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> Message-ID: <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Dang, I forgot about that. Unfortunately, I don't think that works for some other Python packages. On June 11, 2015 11:44:38 AM CDT, Romain Guillebert wrote: >pypy -m pip works > >On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez >wrote: >> I don't think you can out-of-the-box without some env tool. Blame >apt-get's >> brilliant engineering. Since I'm generally allergic to binaries (I.e. >THEY >> DON'T WORK! [which is probably why Torvalds never distributes app >binaries >> for Linux]), I do things the simple way: build it myself. Takes about >45 >> mins. Always works. pip and pytest and such will all get installed >into the >> source directory/bin, NOT /usr/local. In order to access them easily, >I put >> something like this in my .bashrc: >> >> for bin in $STUFF/pypy/bin; do >> alias pypy-${bin##*/}=$bin >> done >> >> # Laziness >> alias pypy="$STUFF/pypy/pypy-c" >> # it was either that or: >> alias pypy="$STUFF/pypy/bin/pypy-c" >> >> >> >> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>> >>> As far as I know scripts don't get installed to site packages (at >least on >>> windows). >>> >>> In other words: say I installed pypy on Ubuntu with nose in it. I >want to >>> launch the nosetests script. (I also have one for the system >Python.) How do >>> I launch the nosetests that belongs to PyPy? >>> >>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" >wrote: >>>> >>>> you can install pypy with apt-get. Stuff gets installed in >>>> site-packages I believe (just like on cpython) >>>> >>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>> > Things I don't care about so much right now: >>>> > - How fast PyPy runs. >>>> > >>>> > Things I care a lot about right now: >>>> > - How many hours of my life I need to spend to get PyPy to run. >>>> > >>>> > On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>> > wrote: >>>> >> >>>> >> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>> >> >>>> >> >>>> >> On June 11, 2015 9:27:12 AM CDT, Ram Rachum >wrote: >>>> >>> >>>> >>> When I install Pypy on Ubuntu using apt-get, and then run >get-pip.py >>>> >>> , >>>> >>> how do I access the pip that belongs to PyPy? >>>> >>> >>>> >>> ________________________________ >>>> >>> >>>> >>> pypy-dev mailing list >>>> >>> pypy-dev at python.org >>>> >>> https://mail.python.org/mailman/listinfo/pypy-dev >>>> >> >>>> >> >>>> >> -- >>>> >> Sent from my Android device with K-9 Mail. Please excuse my >brevity. >>>> > >>>> > >>>> > >>>> > _______________________________________________ >>>> > pypy-dev mailing list >>>> > pypy-dev at python.org >>>> > https://mail.python.org/mailman/listinfo/pypy-dev >>>> > >> >> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 19:52:50 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 20:52:50 +0300 Subject: [pypy-dev] Question In-Reply-To: <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: Unfortunately it doesn't work for nosetests. I've sent a message to python-ideas about this, maybe the -m flag should be changed to work on scripts. I tried a few things, including pyenv, but it didn't work. I've given up at this point. Thanks for your help. On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez wrote: > Dang, I forgot about that. Unfortunately, I don't think that works for > some other Python packages. > > > On June 11, 2015 11:44:38 AM CDT, Romain Guillebert > wrote: >> >> pypy -m pip works >> >> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >> >>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>> mins. Always works. pip and pytest and such will all get installed into the >>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>> something like this in my .bashrc: >>> >>> for bin in $STUFF/pypy/bin; do >>> alias pypy-${bin##*/}=$bin >>> done >>> >>> # Laziness >>> alias pypy="$STUFF/pypy/pypy-c" >>> # it was either that or: >>> alias pypy="$STUFF/pypy/bin/pyp >>> y-c" >>> >>> >>> >>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>> >>>> >>>> As far as I know scripts don't get installed to site packages (at least on >>>> windows). >>>> >>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>> launch the nosetests script. (I also have one for the system Python.) How do >>>> I launch the nosetests that belongs to PyPy? >>>> >>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>> >>>>> >>>>> you can install pypy with apt-get. Stuff gets installed in >>>>> site-packages I believe (just like on cpython) >>>>> >>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>> >>>>>> Things I don't care about so much right now: >>>>>> - How fast PyPy runs. >>>>>> >>>>>> Things I care a lot about right now: >>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>> >>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>> >>>>>>> >>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>> >>>>>>>> >>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>> , >>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>> >>>>>>>> ------------------------------ >>>>>>>> >>>>>>>> >>>>>>>> pypy-dev mai >>>>>>>> ling >>>>>>>> list >>>>>>>> pypy-dev at python.org >>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> ------------------------------ >>>>>> >>>>>> pypy-dev mailing list >>>>>> pypy-dev at python.org >>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>> >>>>> >>>>> >>> >>> -- >>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>> >>> ------------------------------ >>> >>> pypy-dev mailing list >>> pypy-dev at python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >> >> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Thu Jun 11 20:30:56 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 13:30:56 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: Remember: I am *dead* serious about you rebuilding it. If you're on Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you to try. On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: > Unfortunately it doesn't work for nosetests. I've sent a message to > python-ideas about this, maybe the -m flag should be changed to work on > scripts. > > I tried a few things, including pyenv, but it didn't work. I've given up > at this point. Thanks for your help. > > > On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez wrote: > >> Dang, I forgot about that. Unfortunately, I don't think that works for >> some other Python packages. >> >> >> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >> wrote: >>> >>> pypy -m pip works >>> >>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>> >>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>> mins. Always works. pip and pytest and such will all get installed into the >>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>> something like this in my .bashrc: >>>> >>>> for bin in $STUFF/pypy/bin; do >>>> alias pypy-${bin##*/}=$bin >>>> done >>>> >>>> # Laziness >>>> alias pypy="$STUFF/pypy/pypy-c" >>>> # it was either that or: >>>> alias pypy="$STUFF/pypy/bin/pyp >>>> y-c" >>>> >>>> >>>> >>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>> >>>>> >>>>> As far as I know scripts don't get installed to site packages (at least on >>>>> windows). >>>>> >>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>> I launch the nosetests that belongs to PyPy? >>>>> >>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>> >>>>>> >>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>> site-packages I believe (just like on cpython) >>>>>> >>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>> >>>>>>> Things I don't care about so much right now: >>>>>>> - How fast PyPy runs. >>>>>>> >>>>>>> Things I care a lot about right now: >>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>> wrote: >>>>>>> >>>>>>>> >>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>> >>>>>>>> >>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>> , >>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>> >>>>>>>>> ------------------------------ >>>>>>>>> >>>>>>>>> >>>>>>>>> pypy-dev mai >>>>>>>>> ling >>>>>>>>> list >>>>>>>>> pypy-dev at python.org >>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> ------------------------------ >>>>>>> >>>>>>> pypy-dev mailing list >>>>>>> pypy-dev at python.org >>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>> >>>>>> >>>>>> >>>> >>>> -- >>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>> >>>> ------------------------------ >>>> >>>> pypy-dev mailing list >>>> pypy-dev at python.org >>>> https://mail.python.org/mailman/listinfo/pypy-dev >>> >>> >>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> > > -- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something?s wrong. http://kirbyfan64.github.io/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 20:34:34 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 21:34:34 +0300 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: I suck at building. I don't know C. There are likely to be errors that I wouldn't know how to deal with. I'm not interested in wasting another hour trying to deal with those. I'm on Ubuntu 15.04. Thanks for the offer. Hopefully instead of investing so much development effort making PyPy x8 times faster than CPython instead of x7 faster, there'll be more effort to make PyPy easier to install. This also goes for Windows: Why isn't there an installer? But yeah, it's an open-source project, so I'm just ranting. On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez wrote: > Remember: I am *dead* serious about you rebuilding it. If you're on Ubuntu > 14 LTS x64, I can email you the binaries I built that *work* for you to try. > > > On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: > >> Unfortunately it doesn't work for nosetests. I've sent a message to >> python-ideas about this, maybe the -m flag should be changed to work on >> scripts. >> >> I tried a few things, including pyenv, but it didn't work. I've given up >> at this point. Thanks for your help. >> >> >> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez wrote: >> >>> Dang, I forgot about that. Unfortunately, I don't think that works for >>> some other Python packages. >>> >>> >>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>> wrote: >>>> >>>> pypy -m pip works >>>> >>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>> >>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>> something like this in my .bashrc: >>>>> >>>>> for bin in $STUFF/pypy/bin; do >>>>> alias pypy-${bin##*/}=$bin >>>>> done >>>>> >>>>> # Laziness >>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>> # it was either that or: >>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>> y-c" >>>>> >>>>> >>>>> >>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>> >>>>>> >>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>> windows). >>>>>> >>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>> I launch the nosetests that belongs to PyPy? >>>>>> >>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>> >>>>>>> >>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>> site-packages I believe (just like on cpython) >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>> >>>>>>>> Things I don't care about so much right now: >>>>>>>> - How fast PyPy runs. >>>>>>>> >>>>>>>> Things I care a lot about right now: >>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>> wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>> >>>>>>>>> >>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>> , >>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>> >>>>>>>>>> ------------------------------ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> pypy-dev mai >>>>>>>>>> ling >>>>>>>>>> list >>>>>>>>>> pypy-dev at python.org >>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ------------------------------ >>>>>>>> >>>>>>>> pypy-dev mailing list >>>>>>>> pypy-dev at python.org >>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> -- >>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>> >>>>> ------------------------------ >>>>> >>>>> pypy-dev mailing list >>>>> pypy-dev at python.org >>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>> >>>> >>>> >>> -- >>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>> >> >> > > > -- > Ryan > [ERROR]: Your autotools build scripts are 200 lines longer than your > program. Something?s wrong. > http://kirbyfan64.github.io/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Thu Jun 11 20:39:51 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 13:39:51 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: Honestly, these is just general Linux issues. Like I said, not even Linus Torvalds makes binaries of his dive logger for Linux. It a pain in the everything. I usually have the *worst* luck building stuff, but PyPy was actually very easy. I ran `make` and it "just worked". You don't need to know C. Even if you did, trying to edit the C code generated by RPython would be suicide. On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: > I suck at building. I don't know C. There are likely to be errors that I > wouldn't know how to deal with. I'm not interested in wasting another hour > trying to deal with those. > > I'm on Ubuntu 15.04. Thanks for the offer. > > Hopefully instead of investing so much development effort making PyPy x8 > times faster than CPython instead of x7 faster, there'll be more effort to > make PyPy easier to install. This also goes for Windows: Why isn't there an > installer? But yeah, it's an open-source project, so I'm just ranting. > > On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez wrote: > >> Remember: I am *dead* serious about you rebuilding it. If you're on >> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >> to try. >> >> >> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >> >>> Unfortunately it doesn't work for nosetests. I've sent a message to >>> python-ideas about this, maybe the -m flag should be changed to work on >>> scripts. >>> >>> I tried a few things, including pyenv, but it didn't work. I've given up >>> at this point. Thanks for your help. >>> >>> >>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez wrote: >>> >>>> Dang, I forgot about that. Unfortunately, I don't think that works for >>>> some other Python packages. >>>> >>>> >>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>> gmail.com> wrote: >>>>> >>>>> pypy -m pip works >>>>> >>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>> >>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>> something like this in my .bashrc: >>>>>> >>>>>> for bin in $STUFF/pypy/bin; do >>>>>> alias pypy-${bin##*/}=$bin >>>>>> done >>>>>> >>>>>> # Laziness >>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>> # it was either that or: >>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>> y-c" >>>>>> >>>>>> >>>>>> >>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>> >>>>>>> >>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>> windows). >>>>>>> >>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>> >>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>> >>>>>>>> >>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>> site-packages I believe (just like on cpython) >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>> >>>>>>>>> Things I don't care about so much right now: >>>>>>>>> - How fast PyPy runs. >>>>>>>>> >>>>>>>>> Things I care a lot about right now: >>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>> , >>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>> >>>>>>>>>>> ------------------------------ >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> pypy-dev mai >>>>>>>>>>> ling >>>>>>>>>>> list >>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> ------------------------------ >>>>>>>>> >>>>>>>>> pypy-dev mailing list >>>>>>>>> pypy-dev at python.org >>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>> >>>>>>>> >>>>>>>> >>>>>> >>>>>> -- >>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>> >>>>>> ------------------------------ >>>>>> >>>>>> pypy-dev mailing list >>>>>> pypy-dev at python.org >>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>> >>>>> >>>>> >>>> -- >>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>> >>> >>> >> >> >> -- >> Ryan >> [ERROR]: Your autotools build scripts are 200 lines longer than your >> program. Something?s wrong. >> http://kirbyfan64.github.io/ >> >> > > -- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something?s wrong. http://kirbyfan64.github.io/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Thu Jun 11 20:43:59 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 13:43:59 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez wrote: > Honestly, these is just general Linux issues. Like I said, not even Linus > Torvalds makes binaries of his dive logger for Linux. It a pain in the > everything. > *these are* (damn, I hate autocorrect...) > > I usually have the *worst* luck building stuff, but PyPy was actually very > easy. I ran `make` and it "just worked". You don't need to know C. Even if > you did, trying to edit the C code generated by RPython would be suicide. > > > On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: > >> I suck at building. I don't know C. There are likely to be errors that I >> wouldn't know how to deal with. I'm not interested in wasting another hour >> trying to deal with those. >> >> I'm on Ubuntu 15.04. Thanks for the offer. >> >> Hopefully instead of investing so much development effort making PyPy x8 >> times faster than CPython instead of x7 faster, there'll be more effort to >> make PyPy easier to install. This also goes for Windows: Why isn't there an >> installer? But yeah, it's an open-source project, so I'm just ranting. >> >> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez wrote: >> >>> Remember: I am *dead* serious about you rebuilding it. If you're on >>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>> to try. >>> >>> >>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >>> >>>> Unfortunately it doesn't work for nosetests. I've sent a message to >>>> python-ideas about this, maybe the -m flag should be changed to work on >>>> scripts. >>>> >>>> I tried a few things, including pyenv, but it didn't work. I've given >>>> up at this point. Thanks for your help. >>>> >>>> >>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>> wrote: >>>> >>>>> Dang, I forgot about that. Unfortunately, I don't think that works for >>>>> some other Python packages. >>>>> >>>>> >>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>> gmail.com> wrote: >>>>>> >>>>>> pypy -m pip works >>>>>> >>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>> >>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>> something like this in my .bashrc: >>>>>>> >>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>> alias pypy-${bin##*/}=$bin >>>>>>> done >>>>>>> >>>>>>> # Laziness >>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>> # it was either that or: >>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>> y-c" >>>>>>> >>>>>>> >>>>>>> >>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>> >>>>>>>> >>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>> windows). >>>>>>>> >>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>> >>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>> >>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>> - How fast PyPy runs. >>>>>>>>>> >>>>>>>>>> Things I care a lot about right now: >>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>> , >>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------ >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>> ling >>>>>>>>>>>> list >>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> ------------------------------ >>>>>>>>>> >>>>>>>>>> pypy-dev mailing list >>>>>>>>>> pypy-dev at python.org >>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>> >>>>>>> ------------------------------ >>>>>>> >>>>>>> pypy-dev mailing list >>>>>>> pypy-dev at python.org >>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>> >>>>>> >>>>>> >>>>> -- >>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>> >>>> >>>> >>> >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something?s wrong. >>> http://kirbyfan64.github.io/ >>> >>> >> >> > > > -- > Ryan > [ERROR]: Your autotools build scripts are 200 lines longer than your > program. Something?s wrong. > http://kirbyfan64.github.io/ > > -- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something?s wrong. http://kirbyfan64.github.io/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 20:48:58 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 21:48:58 +0300 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: Against my better judgement, I tried following your advice :) Got this error when running make: [translation:ERROR] CompilationError: CompilationError(err=""" [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: fatal error: zlib.h: No such file or directory [translation:ERROR] #include [translation:ERROR] ^ [translation:ERROR] compilation terminated. [translation:ERROR] """) [translation] start debugger... > /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() -> raise last_error (Pdb+) On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez wrote: > On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez wrote: > >> Honestly, these is just general Linux issues. Like I said, not even Linus >> Torvalds makes binaries of his dive logger for Linux. It a pain in the >> everything. >> > > *these are* (damn, I hate autocorrect...) > > >> >> I usually have the *worst* luck building stuff, but PyPy was actually >> very easy. I ran `make` and it "just worked". You don't need to know C. >> Even if you did, trying to edit the C code generated by RPython would be >> suicide. >> >> >> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >> >>> I suck at building. I don't know C. There are likely to be errors that I >>> wouldn't know how to deal with. I'm not interested in wasting another hour >>> trying to deal with those. >>> >>> I'm on Ubuntu 15.04. Thanks for the offer. >>> >>> Hopefully instead of investing so much development effort making PyPy x8 >>> times faster than CPython instead of x7 faster, there'll be more effort to >>> make PyPy easier to install. This also goes for Windows: Why isn't there an >>> installer? But yeah, it's an open-source project, so I'm just ranting. >>> >>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez wrote: >>> >>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>> to try. >>>> >>>> >>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >>>> >>>>> Unfortunately it doesn't work for nosetests. I've sent a message to >>>>> python-ideas about this, maybe the -m flag should be changed to work on >>>>> scripts. >>>>> >>>>> I tried a few things, including pyenv, but it didn't work. I've given >>>>> up at this point. Thanks for your help. >>>>> >>>>> >>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>> wrote: >>>>> >>>>>> Dang, I forgot about that. Unfortunately, I don't think that works >>>>>> for some other Python packages. >>>>>> >>>>>> >>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>> gmail.com> wrote: >>>>>>> >>>>>>> pypy -m pip works >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>> >>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>> something like this in my .bashrc: >>>>>>>> >>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>> done >>>>>>>> >>>>>>>> # Laziness >>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>> # it was either that or: >>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>> y-c" >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>> >>>>>>>>> >>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>> windows). >>>>>>>>> >>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>> >>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>> >>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>> >>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>>> , >>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>> ling >>>>>>>>>>>>> list >>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> ------------------------------ >>>>>>>>>>> >>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>> >>>>>>>> ------------------------------ >>>>>>>> >>>>>>>> pypy-dev mailing list >>>>>>>> pypy-dev at python.org >>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>> >>>>>>> >>>>>>> >>>>>> -- >>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Ryan >>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>> program. Something?s wrong. >>>> http://kirbyfan64.github.io/ >>>> >>>> >>> >>> >> >> >> -- >> Ryan >> [ERROR]: Your autotools build scripts are 200 lines longer than your >> program. Something?s wrong. >> http://kirbyfan64.github.io/ >> >> > > > > -- > Ryan > [ERROR]: Your autotools build scripts are 200 lines longer than your > program. Something?s wrong. > http://kirbyfan64.github.io/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From randall.leeds at gmail.com Thu Jun 11 20:52:39 2015 From: randall.leeds at gmail.com (Randall Leeds) Date: Thu, 11 Jun 2015 18:52:39 +0000 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: The PyPy PPA works brilliantly on 15.04 for me. >From there I just make a virtualenv with: $ virtualenv -P /usr/bin/pypy (Can't remember if it's -P or -p) Once activated, just running pip works fine for me. On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: > Against my better judgement, I tried following your advice :) > > Got this error when running make: > > [translation:ERROR] CompilationError: CompilationError(err=""" > [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: > fatal error: zlib.h: No such file or directory > [translation:ERROR] #include > [translation:ERROR] ^ > [translation:ERROR] compilation terminated. > [translation:ERROR] """) > [translation] start debugger... > > > /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() > -> raise last_error > (Pdb+) > > > > > On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez wrote: > >> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez wrote: >> >>> Honestly, these is just general Linux issues. Like I said, not even >>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>> the everything. >>> >> >> *these are* (damn, I hate autocorrect...) >> >> >>> >>> I usually have the *worst* luck building stuff, but PyPy was actually >>> very easy. I ran `make` and it "just worked". You don't need to know C. >>> Even if you did, trying to edit the C code generated by RPython would be >>> suicide. >>> >>> >>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>> >>>> I suck at building. I don't know C. There are likely to be errors that >>>> I wouldn't know how to deal with. I'm not interested in wasting another >>>> hour trying to deal with those. >>>> >>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>> >>>> Hopefully instead of investing so much development effort making PyPy >>>> x8 times faster than CPython instead of x7 faster, there'll be more effort >>>> to make PyPy easier to install. This also goes for Windows: Why isn't there >>>> an installer? But yeah, it's an open-source project, so I'm just ranting. >>>> >>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>> wrote: >>>> >>>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>>> to try. >>>>> >>>>> >>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >>>>> >>>>>> Unfortunately it doesn't work for nosetests. I've sent a message to >>>>>> python-ideas about this, maybe the -m flag should be changed to work on >>>>>> scripts. >>>>>> >>>>>> I tried a few things, including pyenv, but it didn't work. I've given >>>>>> up at this point. Thanks for your help. >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>> wrote: >>>>>> >>>>>>> Dang, I forgot about that. Unfortunately, I don't think that works >>>>>>> for some other Python packages. >>>>>>> >>>>>>> >>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>> gmail.com> wrote: >>>>>>>> >>>>>>>> pypy -m pip works >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>> >>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>> something like this in my .bashrc: >>>>>>>>> >>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>> done >>>>>>>>> >>>>>>>>> # Laziness >>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>> # it was either that or: >>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>> y-c" >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>> windows). >>>>>>>>>> >>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>> >>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>> >>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>> >>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>>>> , >>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>> ling >>>>>>>>>>>>>> list >>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------ >>>>>>>>>>>> >>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>> >>>>>>>>> ------------------------------ >>>>>>>>> >>>>>>>>> pypy-dev mailing list >>>>>>>>> pypy-dev at python.org >>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- >>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan >>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>> program. Something?s wrong. >>>>> http://kirbyfan64.github.io/ >>>>> >>>>> >>>> >>>> >>> >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something?s wrong. >>> http://kirbyfan64.github.io/ >>> >>> >> >> >> >> -- >> Ryan >> [ERROR]: Your autotools build scripts are 200 lines longer than your >> program. Something?s wrong. >> http://kirbyfan64.github.io/ >> >> > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 20:54:55 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 21:54:55 +0300 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: I have no idea how to use the PyPy PPA. (Not a Linux user here.) On Thu, Jun 11, 2015 at 9:52 PM, Randall Leeds wrote: > The PyPy PPA works brilliantly on 15.04 for me. > > From there I just make a virtualenv with: > > $ virtualenv -P /usr/bin/pypy > > (Can't remember if it's -P or -p) > > Once activated, just running pip works fine for me. > > On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: > >> Against my better judgement, I tried following your advice :) >> >> Got this error when running make: >> >> [translation:ERROR] CompilationError: CompilationError(err=""" >> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >> fatal error: zlib.h: No such file or directory >> [translation:ERROR] #include >> [translation:ERROR] ^ >> [translation:ERROR] compilation terminated. >> [translation:ERROR] """) >> [translation] start debugger... >> > >> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >> -> raise last_error >> (Pdb+) >> >> >> >> >> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez wrote: >> >>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez wrote: >>> >>>> Honestly, these is just general Linux issues. Like I said, not even >>>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>>> the everything. >>>> >>> >>> *these are* (damn, I hate autocorrect...) >>> >>> >>>> >>>> I usually have the *worst* luck building stuff, but PyPy was actually >>>> very easy. I ran `make` and it "just worked". You don't need to know C. >>>> Even if you did, trying to edit the C code generated by RPython would be >>>> suicide. >>>> >>>> >>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>>> >>>>> I suck at building. I don't know C. There are likely to be errors that >>>>> I wouldn't know how to deal with. I'm not interested in wasting another >>>>> hour trying to deal with those. >>>>> >>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>> >>>>> Hopefully instead of investing so much development effort making PyPy >>>>> x8 times faster than CPython instead of x7 faster, there'll be more effort >>>>> to make PyPy easier to install. This also goes for Windows: Why isn't there >>>>> an installer? But yeah, it's an open-source project, so I'm just ranting. >>>>> >>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>> wrote: >>>>> >>>>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>>>> to try. >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >>>>>> >>>>>>> Unfortunately it doesn't work for nosetests. I've sent a message to >>>>>>> python-ideas about this, maybe the -m flag should be changed to work on >>>>>>> scripts. >>>>>>> >>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>> given up at this point. Thanks for your help. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>>> wrote: >>>>>>> >>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that works >>>>>>>> for some other Python packages. >>>>>>>> >>>>>>>> >>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>> gmail.com> wrote: >>>>>>>>> >>>>>>>>> pypy -m pip works >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>> >>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>> something like this in my .bashrc: >>>>>>>>>> >>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>> done >>>>>>>>>> >>>>>>>>>> # Laziness >>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>> # it was either that or: >>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>> y-c" >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>> windows). >>>>>>>>>>> >>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>> >>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>> >>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>>>>> , >>>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>> list >>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>> >>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>> >>>>>>>>>> ------------------------------ >>>>>>>>>> >>>>>>>>>> pypy-dev mailing list >>>>>>>>>> pypy-dev at python.org >>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> -- >>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ryan >>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>> program. Something?s wrong. >>>>>> http://kirbyfan64.github.io/ >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Ryan >>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>> program. Something?s wrong. >>>> http://kirbyfan64.github.io/ >>>> >>>> >>> >>> >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something?s wrong. >>> http://kirbyfan64.github.io/ >>> >>> >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Thu Jun 11 21:01:43 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 14:01:43 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: Ah, minor detail. You need to first run: sudo apt-get install libffi-dev pkg-config libz-dev libbz2-dev \ libsqlite3-dev libncurses-dev libexpat1-dev libssl-dev ;) On Thu, Jun 11, 2015 at 1:48 PM, Ram Rachum wrote: > Against my better judgement, I tried following your advice :) > > Got this error when running make: > > [translation:ERROR] CompilationError: CompilationError(err=""" > [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: > fatal error: zlib.h: No such file or directory > [translation:ERROR] #include > [translation:ERROR] ^ > [translation:ERROR] compilation terminated. > [translation:ERROR] """) > [translation] start debugger... > > > /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() > -> raise last_error > (Pdb+) > > > > > On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez wrote: > >> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez wrote: >> >>> Honestly, these is just general Linux issues. Like I said, not even >>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>> the everything. >>> >> >> *these are* (damn, I hate autocorrect...) >> >> >>> >>> I usually have the *worst* luck building stuff, but PyPy was actually >>> very easy. I ran `make` and it "just worked". You don't need to know C. >>> Even if you did, trying to edit the C code generated by RPython would be >>> suicide. >>> >>> >>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>> >>>> I suck at building. I don't know C. There are likely to be errors that >>>> I wouldn't know how to deal with. I'm not interested in wasting another >>>> hour trying to deal with those. >>>> >>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>> >>>> Hopefully instead of investing so much development effort making PyPy >>>> x8 times faster than CPython instead of x7 faster, there'll be more effort >>>> to make PyPy easier to install. This also goes for Windows: Why isn't there >>>> an installer? But yeah, it's an open-source project, so I'm just ranting. >>>> >>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>> wrote: >>>> >>>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>>> to try. >>>>> >>>>> >>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >>>>> >>>>>> Unfortunately it doesn't work for nosetests. I've sent a message to >>>>>> python-ideas about this, maybe the -m flag should be changed to work on >>>>>> scripts. >>>>>> >>>>>> I tried a few things, including pyenv, but it didn't work. I've given >>>>>> up at this point. Thanks for your help. >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>> wrote: >>>>>> >>>>>>> Dang, I forgot about that. Unfortunately, I don't think that works >>>>>>> for some other Python packages. >>>>>>> >>>>>>> >>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>> gmail.com> wrote: >>>>>>>> >>>>>>>> pypy -m pip works >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>> >>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>> something like this in my .bashrc: >>>>>>>>> >>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>> done >>>>>>>>> >>>>>>>>> # Laziness >>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>> # it was either that or: >>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>> y-c" >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>> >>>>>>>>>> >>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>> windows). >>>>>>>>>> >>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>> >>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>> >>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>> >>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>>>> , >>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>> ling >>>>>>>>>>>>>> list >>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------ >>>>>>>>>>>> >>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>> >>>>>>>>> ------------------------------ >>>>>>>>> >>>>>>>>> pypy-dev mailing list >>>>>>>>> pypy-dev at python.org >>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- >>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan >>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>> program. Something?s wrong. >>>>> http://kirbyfan64.github.io/ >>>>> >>>>> >>>> >>>> >>> >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something?s wrong. >>> http://kirbyfan64.github.io/ >>> >>> >> >> >> >> -- >> Ryan >> [ERROR]: Your autotools build scripts are 200 lines longer than your >> program. Something?s wrong. >> http://kirbyfan64.github.io/ >> >> > > -- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something?s wrong. http://kirbyfan64.github.io/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From randall.leeds at gmail.com Thu Jun 11 21:01:50 2015 From: randall.leeds at gmail.com (Randall Leeds) Date: Thu, 11 Jun 2015 19:01:50 +0000 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: I'm in transit right but I can spell out the directions when I'm settled a little later. On Thu, Jun 11, 2015, 11:55 Ram Rachum wrote: > I have no idea how to use the PyPy PPA. (Not a Linux user here.) > > On Thu, Jun 11, 2015 at 9:52 PM, Randall Leeds > wrote: > >> The PyPy PPA works brilliantly on 15.04 for me. >> >> From there I just make a virtualenv with: >> >> $ virtualenv -P /usr/bin/pypy >> >> (Can't remember if it's -P or -p) >> >> Once activated, just running pip works fine for me. >> >> On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: >> >>> Against my better judgement, I tried following your advice :) >>> >>> Got this error when running make: >>> >>> [translation:ERROR] CompilationError: CompilationError(err=""" >>> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>> fatal error: zlib.h: No such file or directory >>> [translation:ERROR] #include >>> [translation:ERROR] ^ >>> [translation:ERROR] compilation terminated. >>> [translation:ERROR] """) >>> [translation] start debugger... >>> > >>> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>> -> raise last_error >>> (Pdb+) >>> >>> >>> >>> >>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez wrote: >>> >>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>> wrote: >>>> >>>>> Honestly, these is just general Linux issues. Like I said, not even >>>>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>>>> the everything. >>>>> >>>> >>>> *these are* (damn, I hate autocorrect...) >>>> >>>> >>>>> >>>>> I usually have the *worst* luck building stuff, but PyPy was actually >>>>> very easy. I ran `make` and it "just worked". You don't need to know C. >>>>> Even if you did, trying to edit the C code generated by RPython would be >>>>> suicide. >>>>> >>>>> >>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>>>> >>>>>> I suck at building. I don't know C. There are likely to be errors >>>>>> that I wouldn't know how to deal with. I'm not interested in wasting >>>>>> another hour trying to deal with those. >>>>>> >>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>> >>>>>> Hopefully instead of investing so much development effort making PyPy >>>>>> x8 times faster than CPython instead of x7 faster, there'll be more effort >>>>>> to make PyPy easier to install. This also goes for Windows: Why isn't there >>>>>> an installer? But yeah, it's an open-source project, so I'm just ranting. >>>>>> >>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>> wrote: >>>>>> >>>>>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>>>>> to try. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >>>>>>> >>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a message to >>>>>>>> python-ideas about this, maybe the -m flag should be changed to work on >>>>>>>> scripts. >>>>>>>> >>>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>>> given up at this point. Thanks for your help. >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that works >>>>>>>>> for some other Python packages. >>>>>>>>> >>>>>>>>> >>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>> gmail.com> wrote: >>>>>>>>>> >>>>>>>>>> pypy -m pip works >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>>> >>>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>>> something like this in my .bashrc: >>>>>>>>>>> >>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>> done >>>>>>>>>>> >>>>>>>>>>> # Laziness >>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>> # it was either that or: >>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>> y-c" >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>>> windows). >>>>>>>>>>>> >>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>> >>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>>>>>> , >>>>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>> list >>>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>> >>>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>> >>>>>>>>>>> ------------------------------ >>>>>>>>>>> >>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>> brevity. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ryan >>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>>> program. Something?s wrong. >>>>>>> http://kirbyfan64.github.io/ >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan >>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>> program. Something?s wrong. >>>>> http://kirbyfan64.github.io/ >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Ryan >>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>> program. Something?s wrong. >>>> http://kirbyfan64.github.io/ >>>> >>>> >>> >>> _______________________________________________ >>> pypy-dev mailing list >>> pypy-dev at python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 21:05:07 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 22:05:07 +0300 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: Okay, I'll try it. (Once I add more resources to the VM so it could finish faster.) On Thu, Jun 11, 2015 at 10:01 PM, Ryan Gonzalez wrote: > Ah, minor detail. You need to first run: > > sudo apt-get install libffi-dev pkg-config libz-dev libbz2-dev \ > libsqlite3-dev libncurses-dev libexpat1-dev libssl-dev > > ;) > > > On Thu, Jun 11, 2015 at 1:48 PM, Ram Rachum wrote: > >> Against my better judgement, I tried following your advice :) >> >> Got this error when running make: >> >> [translation:ERROR] CompilationError: CompilationError(err=""" >> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >> fatal error: zlib.h: No such file or directory >> [translation:ERROR] #include >> [translation:ERROR] ^ >> [translation:ERROR] compilation terminated. >> [translation:ERROR] """) >> [translation] start debugger... >> > >> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >> -> raise last_error >> (Pdb+) >> >> >> >> >> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez wrote: >> >>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez wrote: >>> >>>> Honestly, these is just general Linux issues. Like I said, not even >>>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>>> the everything. >>>> >>> >>> *these are* (damn, I hate autocorrect...) >>> >>> >>>> >>>> I usually have the *worst* luck building stuff, but PyPy was actually >>>> very easy. I ran `make` and it "just worked". You don't need to know C. >>>> Even if you did, trying to edit the C code generated by RPython would be >>>> suicide. >>>> >>>> >>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>>> >>>>> I suck at building. I don't know C. There are likely to be errors that >>>>> I wouldn't know how to deal with. I'm not interested in wasting another >>>>> hour trying to deal with those. >>>>> >>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>> >>>>> Hopefully instead of investing so much development effort making PyPy >>>>> x8 times faster than CPython instead of x7 faster, there'll be more effort >>>>> to make PyPy easier to install. This also goes for Windows: Why isn't there >>>>> an installer? But yeah, it's an open-source project, so I'm just ranting. >>>>> >>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>> wrote: >>>>> >>>>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>>>> to try. >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >>>>>> >>>>>>> Unfortunately it doesn't work for nosetests. I've sent a message to >>>>>>> python-ideas about this, maybe the -m flag should be changed to work on >>>>>>> scripts. >>>>>>> >>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>> given up at this point. Thanks for your help. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>>> wrote: >>>>>>> >>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that works >>>>>>>> for some other Python packages. >>>>>>>> >>>>>>>> >>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>> gmail.com> wrote: >>>>>>>>> >>>>>>>>> pypy -m pip works >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>> >>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>> something like this in my .bashrc: >>>>>>>>>> >>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>> done >>>>>>>>>> >>>>>>>>>> # Laziness >>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>> # it was either that or: >>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>> y-c" >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>> windows). >>>>>>>>>>> >>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>> >>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>> >>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>>>>> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>>>>> , >>>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>> list >>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>> >>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>> >>>>>>>>>> ------------------------------ >>>>>>>>>> >>>>>>>>>> pypy-dev mailing list >>>>>>>>>> pypy-dev at python.org >>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> -- >>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ryan >>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>> program. Something?s wrong. >>>>>> http://kirbyfan64.github.io/ >>>>>> >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Ryan >>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>> program. Something?s wrong. >>>> http://kirbyfan64.github.io/ >>>> >>>> >>> >>> >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something?s wrong. >>> http://kirbyfan64.github.io/ >>> >>> >> >> > > > -- > Ryan > [ERROR]: Your autotools build scripts are 200 lines longer than your > program. Something?s wrong. > http://kirbyfan64.github.io/ > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Thu Jun 11 21:08:56 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 14:08:56 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: <968F7C54-FC07-45AF-902E-26787D28FF56@gmail.com> sudo add-apt-repository ppa:pypy/ppa sudo apt-get update On June 11, 2015 1:54:55 PM CDT, Ram Rachum wrote: >I have no idea how to use the PyPy PPA. (Not a Linux user here.) > >On Thu, Jun 11, 2015 at 9:52 PM, Randall Leeds > >wrote: > >> The PyPy PPA works brilliantly on 15.04 for me. >> >> From there I just make a virtualenv with: >> >> $ virtualenv -P /usr/bin/pypy >> >> (Can't remember if it's -P or -p) >> >> Once activated, just running pip works fine for me. >> >> On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: >> >>> Against my better judgement, I tried following your advice :) >>> >>> Got this error when running make: >>> >>> [translation:ERROR] CompilationError: CompilationError(err=""" >>> [translation:ERROR] >/tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>> fatal error: zlib.h: No such file or directory >>> [translation:ERROR] #include >>> [translation:ERROR] ^ >>> [translation:ERROR] compilation terminated. >>> [translation:ERROR] """) >>> [translation] start debugger... >>> > >>> >/home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>> -> raise last_error >>> (Pdb+) >>> >>> >>> >>> >>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez >wrote: >>> >>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >wrote: >>>> >>>>> Honestly, these is just general Linux issues. Like I said, not >even >>>>> Linus Torvalds makes binaries of his dive logger for Linux. It a >pain in >>>>> the everything. >>>>> >>>> >>>> *these are* (damn, I hate autocorrect...) >>>> >>>> >>>>> >>>>> I usually have the *worst* luck building stuff, but PyPy was >actually >>>>> very easy. I ran `make` and it "just worked". You don't need to >know C. >>>>> Even if you did, trying to edit the C code generated by RPython >would be >>>>> suicide. >>>>> >>>>> >>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum >wrote: >>>>> >>>>>> I suck at building. I don't know C. There are likely to be errors >that >>>>>> I wouldn't know how to deal with. I'm not interested in wasting >another >>>>>> hour trying to deal with those. >>>>>> >>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>> >>>>>> Hopefully instead of investing so much development effort making >PyPy >>>>>> x8 times faster than CPython instead of x7 faster, there'll be >more effort >>>>>> to make PyPy easier to install. This also goes for Windows: Why >isn't there >>>>>> an installer? But yeah, it's an open-source project, so I'm just >ranting. >>>>>> >>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>> wrote: >>>>>> >>>>>>> Remember: I am *dead* serious about you rebuilding it. If you're >on >>>>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that >*work* for you >>>>>>> to try. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum >wrote: >>>>>>> >>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a >message to >>>>>>>> python-ideas about this, maybe the -m flag should be changed to >work on >>>>>>>> scripts. >>>>>>>> >>>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>>> given up at this point. Thanks for your help. >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez > >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that >works >>>>>>>>> for some other Python packages. >>>>>>>>> >>>>>>>>> >>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>>> gmail.com> wrote: >>>>>>>>>> >>>>>>>>>> pypy -m pip works >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez > wrote: >>>>>>>>>> >>>>>>>>>>> I don't think you can out-of-the-box without some env tool. >Blame apt-get's >>>>>>>>>>> brilliant engineering. Since I'm generally allergic to >binaries (I.e. THEY >>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never >distributes app binaries >>>>>>>>>>> for Linux]), I do things the simple way: build it myself. >Takes about 45 >>>>>>>>>>> mins. Always works. pip and pytest and such will all get >installed into the >>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access >them easily, I put >>>>>>>>>>> something like this in my .bashrc: >>>>>>>>>>> >>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>> done >>>>>>>>>>> >>>>>>>>>>> # Laziness >>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>> # it was either that or: >>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>> y-c" >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum > wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> As far as I know scripts don't get installed to site >packages (at least on >>>>>>>>>>>> windows). >>>>>>>>>>>> >>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose >in it. I want to >>>>>>>>>>>> launch the nosetests script. (I also have one for the >system Python.) How do >>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>> >>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" > wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed >in >>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum > wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>> - How many hours of my life I need to spend to get PyPy >to run. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez > >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely >slow. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum > wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then >run get-pip.py >>>>>>>>>>>>>>>> , >>>>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>> list >>>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please >excuse my brevity. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>> >>>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >brevity. >>>>>>>>>>> >>>>>>>>>>> ------------------------------ >>>>>>>>>>> >>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >brevity. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ryan >>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >your >>>>>>> program. Something?s wrong. >>>>>>> http://kirbyfan64.github.io/ >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan >>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >your >>>>> program. Something?s wrong. >>>>> http://kirbyfan64.github.io/ >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Ryan >>>> [ERROR]: Your autotools build scripts are 200 lines longer than >your >>>> program. Something?s wrong. >>>> http://kirbyfan64.github.io/ >>>> >>>> >>> >>> _______________________________________________ >>> pypy-dev mailing list >>> pypy-dev at python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >>> >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 21:12:20 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 22:12:20 +0300 Subject: [pypy-dev] Question In-Reply-To: <968F7C54-FC07-45AF-902E-26787D28FF56@gmail.com> References: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> <968F7C54-FC07-45AF-902E-26787D28FF56@gmail.com> Message-ID: When you use the ppa, where will nosetests be located? On Thu, Jun 11, 2015 at 10:08 PM, Ryan Gonzalez wrote: > sudo add-apt-repository ppa:pypy/ppa > sudo apt-get update > > > > On June 11, 2015 1:54:55 PM CDT, Ram Rachum wrote: >> >> I have no idea how to use the PyPy PPA. (Not a Linux user here.) >> >> On Thu, Jun 11, 2015 at 9:52 PM, Randall Leeds >> wrote: >> >>> The PyPy PPA works brilliantly on 15.04 for me. >>> >>> From there I just make a virtualenv with: >>> >>> $ virtualenv -P /usr/bin/pypy >>> >>> (Can't remember if it's -P or -p) >>> >>> Once activated, just running pip works fine for me. >>> >>> On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: >>> >>>> Against my better judgement, I tried following your advice :) >>>> >>>> Got this error when running make: >>>> >>>> [translation:ERROR] CompilationError: CompilationError(err=""" >>>> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>>> fatal error: zlib.h: No such file or directory >>>> [translation:ERROR] #include >>>> [translation:ERROR] ^ >>>> [translation:ERROR] compilation terminated. >>>> [translation:ERROR] """) >>>> [translation] start debugger... >>>> > >>>> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>>> -> raise last_error >>>> (Pdb+) >>>> >>>> >>>> >>>> >>>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez >>>> wrote: >>>> >>>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>>> wrote: >>>>> >>>>>> Honestly, these is just general Linux issues. Like I said, not even >>>>>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>>>>> the everything. >>>>>> >>>>> >>>>> *these are* (damn, I hate autocorrect...) >>>>> >>>>> >>>>>> >>>>>> I usually have the *worst* luck building stuff, but PyPy was actually >>>>>> very easy. I ran `make` and it "just worked". You don't need to know C. >>>>>> Even if you did, trying to edit the C code generated by RPython would be >>>>>> suicide. >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>>>>> >>>>>>> I suck at building. I don't know C. There are likely to be errors >>>>>>> that I wouldn't know how to deal with. I'm not interested in wasting >>>>>>> another hour trying to deal with those. >>>>>>> >>>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>>> >>>>>>> Hopefully instead of investing so much development effort making >>>>>>> PyPy x8 times faster than CPython instead of x7 faster, there'll be more >>>>>>> effort to make PyPy easier to install. This also goes for Windows: Why >>>>>>> isn't there an installer? But yeah, it's an open-source project, so I'm >>>>>>> just ranting. >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>>> wrote: >>>>>>> >>>>>>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>>>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>>>>>> to try. >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a message >>>>>>>>> to python-ideas about this, maybe the -m flag should be changed to work on >>>>>>>>> scripts. >>>>>>>>> >>>>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>>>> given up at this point. Thanks for your help. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that >>>>>>>>>> works for some other Python packages. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>>> gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>> pypy -m pip works >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>>>> >>>>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>>>> something like this in my .bashr >>>>>>>>>>>> c: >>>>>>>>>>>> >>>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>>> done >>>>>>>>>>>> >>>>>>>>>>>> # Laziness >>>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>>> # it was either that or: >>>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>>> y-c" >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>>>> windows). >>>>>>>>>>>>> >>>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>>> >>>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> * - >>>>>>>>>>>>>>> How many hours of my life I need to spend to get PyPy to run. On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez > wrote: Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. On June 11, 2015 9:27:12 AM CDT, Ram Rachum > wrote: When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , how do I access the pip that belongs to PyPy?------------------------------ pypy-dev mai >>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>> list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity.------------------------------ pypy-dev mailing list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev * >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------ >>>>>>>>>>>> >>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>>> brevity. >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Ryan >>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>> your program. Something?s wrong. >>>>>>>> http://kirbyfan64.github.io/ >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ryan >>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>> program. Something?s wrong. >>>>>> http://kirbyfan64.github.io/ >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan >>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>> program. Something?s wrong. >>>>> http://kirbyfan64.github.io/ >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> pypy-dev mailing list >>>> pypy-dev at python.org >>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>> >>> >> > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phyo.arkarlwin at gmail.com Thu Jun 11 21:13:51 2015 From: phyo.arkarlwin at gmail.com (Phyo Arkar) Date: Fri, 12 Jun 2015 01:43:51 +0630 Subject: [pypy-dev] Question In-Reply-To: References: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> <968F7C54-FC07-45AF-902E-26787D28FF56@gmail.com> Message-ID: Have you tried portable pypy ? https://github.com/squeaky-pl/portable-pypy it works for me , in every linuxes. On Fri, Jun 12, 2015 at 1:42 AM, Ram Rachum wrote: > When you use the ppa, where will nosetests be located? > > On Thu, Jun 11, 2015 at 10:08 PM, Ryan Gonzalez wrote: > >> sudo add-apt-repository ppa:pypy/ppa >> sudo apt-get update >> >> >> >> On June 11, 2015 1:54:55 PM CDT, Ram Rachum wrote: >>> >>> I have no idea how to use the PyPy PPA. (Not a Linux user here.) >>> >>> On Thu, Jun 11, 2015 at 9:52 PM, Randall Leeds >>> wrote: >>> >>>> The PyPy PPA works brilliantly on 15.04 for me. >>>> >>>> From there I just make a virtualenv with: >>>> >>>> $ virtualenv -P /usr/bin/pypy >>>> >>>> (Can't remember if it's -P or -p) >>>> >>>> Once activated, just running pip works fine for me. >>>> >>>> On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: >>>> >>>>> Against my better judgement, I tried following your advice :) >>>>> >>>>> Got this error when running make: >>>>> >>>>> [translation:ERROR] CompilationError: CompilationError(err=""" >>>>> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>>>> fatal error: zlib.h: No such file or directory >>>>> [translation:ERROR] #include >>>>> [translation:ERROR] ^ >>>>> [translation:ERROR] compilation terminated. >>>>> [translation:ERROR] """) >>>>> [translation] start debugger... >>>>> > >>>>> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>>>> -> raise last_error >>>>> (Pdb+) >>>>> >>>>> >>>>> >>>>> >>>>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez >>>>> wrote: >>>>> >>>>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>>>> wrote: >>>>>> >>>>>>> Honestly, these is just general Linux issues. Like I said, not even >>>>>>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>>>>>> the everything. >>>>>>> >>>>>> >>>>>> *these are* (damn, I hate autocorrect...) >>>>>> >>>>>> >>>>>>> >>>>>>> I usually have the *worst* luck building stuff, but PyPy was >>>>>>> actually very easy. I ran `make` and it "just worked". You don't need to >>>>>>> know C. Even if you did, trying to edit the C code generated by RPython >>>>>>> would be suicide. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>>>>>> >>>>>>>> I suck at building. I don't know C. There are likely to be errors >>>>>>>> that I wouldn't know how to deal with. I'm not interested in wasting >>>>>>>> another hour trying to deal with those. >>>>>>>> >>>>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>>>> >>>>>>>> Hopefully instead of investing so much development effort making >>>>>>>> PyPy x8 times faster than CPython instead of x7 faster, there'll be more >>>>>>>> effort to make PyPy easier to install. This also goes for Windows: Why >>>>>>>> isn't there an installer? But yeah, it's an open-source project, so I'm >>>>>>>> just ranting. >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Remember: I am *dead* serious about you rebuilding it. If you're >>>>>>>>> on Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for >>>>>>>>> you to try. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a message >>>>>>>>>> to python-ideas about this, maybe the -m flag should be changed to work on >>>>>>>>>> scripts. >>>>>>>>>> >>>>>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>>>>> given up at this point. Thanks for your help. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that >>>>>>>>>>> works for some other Python packages. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>>>> gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>> pypy -m pip works >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>>>>> >>>>>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>>>>> something like this in my .bashr >>>>>>>>>>>>> c: >>>>>>>>>>>>> >>>>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>>>> done >>>>>>>>>>>>> >>>>>>>>>>>>> # Laziness >>>>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>>>> # it was either that or: >>>>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>>>> y-c" >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>>>>> windows). >>>>>>>>>>>>>> >>>>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> * - >>>>>>>>>>>>>>>> How many hours of my life I need to spend to get PyPy to run. On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez > wrote: Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. On June 11, 2015 9:27:12 AM CDT, Ram Rachum > wrote: When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , how do I access the pip that belongs to PyPy?------------------------------ pypy-dev mai >>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>> list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity.------------------------------ pypy-dev mailing list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev * >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>> >>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>> >>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>>>> brevity. >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Ryan >>>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>>> your program. Something?s wrong. >>>>>>>>> http://kirbyfan64.github.io/ >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ryan >>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>>> program. Something?s wrong. >>>>>>> http://kirbyfan64.github.io/ >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ryan >>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>> program. Something?s wrong. >>>>>> http://kirbyfan64.github.io/ >>>>>> >>>>>> >>>>> >>>>> _______________________________________________ >>>>> pypy-dev mailing list >>>>> pypy-dev at python.org >>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>> >>>> >>> >> -- >> Sent from my Android device with K-9 Mail. Please excuse my brevity. >> > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phyo.arkarlwin at gmail.com Thu Jun 11 21:14:24 2015 From: phyo.arkarlwin at gmail.com (Phyo Arkar) Date: Fri, 12 Jun 2015 01:44:24 +0630 Subject: [pypy-dev] Question In-Reply-To: References: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> <968F7C54-FC07-45AF-902E-26787D28FF56@gmail.com> Message-ID: It is just Download , extract , Run, and have fun. On Fri, Jun 12, 2015 at 1:43 AM, Phyo Arkar wrote: > Have you tried portable pypy ? https://github.com/squeaky-pl/portable-pypy > it works for me , in every linuxes. > > On Fri, Jun 12, 2015 at 1:42 AM, Ram Rachum wrote: > >> When you use the ppa, where will nosetests be located? >> >> On Thu, Jun 11, 2015 at 10:08 PM, Ryan Gonzalez wrote: >> >>> sudo add-apt-repository ppa:pypy/ppa >>> sudo apt-get update >>> >>> >>> >>> On June 11, 2015 1:54:55 PM CDT, Ram Rachum wrote: >>>> >>>> I have no idea how to use the PyPy PPA. (Not a Linux user here.) >>>> >>>> On Thu, Jun 11, 2015 at 9:52 PM, Randall Leeds >>> > wrote: >>>> >>>>> The PyPy PPA works brilliantly on 15.04 for me. >>>>> >>>>> From there I just make a virtualenv with: >>>>> >>>>> $ virtualenv -P /usr/bin/pypy >>>>> >>>>> (Can't remember if it's -P or -p) >>>>> >>>>> Once activated, just running pip works fine for me. >>>>> >>>>> On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: >>>>> >>>>>> Against my better judgement, I tried following your advice :) >>>>>> >>>>>> Got this error when running make: >>>>>> >>>>>> [translation:ERROR] CompilationError: CompilationError(err=""" >>>>>> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>>>>> fatal error: zlib.h: No such file or directory >>>>>> [translation:ERROR] #include >>>>>> [translation:ERROR] ^ >>>>>> [translation:ERROR] compilation terminated. >>>>>> [translation:ERROR] """) >>>>>> [translation] start debugger... >>>>>> > >>>>>> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>>>>> -> raise last_error >>>>>> (Pdb+) >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez >>>>>> wrote: >>>>>> >>>>>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>>>>> wrote: >>>>>>> >>>>>>>> Honestly, these is just general Linux issues. Like I said, not even >>>>>>>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>>>>>>> the everything. >>>>>>>> >>>>>>> >>>>>>> *these are* (damn, I hate autocorrect...) >>>>>>> >>>>>>> >>>>>>>> >>>>>>>> I usually have the *worst* luck building stuff, but PyPy was >>>>>>>> actually very easy. I ran `make` and it "just worked". You don't need to >>>>>>>> know C. Even if you did, trying to edit the C code generated by RPython >>>>>>>> would be suicide. >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>>>>>>> >>>>>>>>> I suck at building. I don't know C. There are likely to be errors >>>>>>>>> that I wouldn't know how to deal with. I'm not interested in wasting >>>>>>>>> another hour trying to deal with those. >>>>>>>>> >>>>>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>>>>> >>>>>>>>> Hopefully instead of investing so much development effort making >>>>>>>>> PyPy x8 times faster than CPython instead of x7 faster, there'll be more >>>>>>>>> effort to make PyPy easier to install. This also goes for Windows: Why >>>>>>>>> isn't there an installer? But yeah, it's an open-source project, so I'm >>>>>>>>> just ranting. >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Remember: I am *dead* serious about you rebuilding it. If you're >>>>>>>>>> on Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for >>>>>>>>>> you to try. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a message >>>>>>>>>>> to python-ideas about this, maybe the -m flag should be changed to work on >>>>>>>>>>> scripts. >>>>>>>>>>> >>>>>>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>>>>>> given up at this point. Thanks for your help. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>>>>>> > wrote: >>>>>>>>>>> >>>>>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that >>>>>>>>>>>> works for some other Python packages. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>>>>> gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> pypy -m pip works >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>>>>>> something like this in my .bashr >>>>>>>>>>>>>> c: >>>>>>>>>>>>>> >>>>>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>>>>> done >>>>>>>>>>>>>> >>>>>>>>>>>>>> # Laziness >>>>>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>>>>> # it was either that or: >>>>>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>>>>> y-c" >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>>>>>> windows). >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> * - >>>>>>>>>>>>>>>>> How many hours of my life I need to spend to get PyPy to run. On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez > wrote: Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. On June 11, 2015 9:27:12 AM CDT, Ram Rachum > wrote: When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , how do I access the pip that belongs to PyPy?------------------------------ pypy-dev mai >>>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>>> list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity.------------------------------ pypy-dev mailing list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev * >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>> >>>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>>>>> brevity. >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Ryan >>>>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>>>> your program. Something?s wrong. >>>>>>>>>> http://kirbyfan64.github.io/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Ryan >>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>> your program. Something?s wrong. >>>>>>>> http://kirbyfan64.github.io/ >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ryan >>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>>> program. Something?s wrong. >>>>>>> http://kirbyfan64.github.io/ >>>>>>> >>>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> pypy-dev mailing list >>>>>> pypy-dev at python.org >>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>> >>>>> >>>> >>> -- >>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>> >> >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 21:17:58 2015 From: ram at rachum.com (Ram Rachum) Date: Thu, 11 Jun 2015 22:17:58 +0300 Subject: [pypy-dev] Question In-Reply-To: References: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> <968F7C54-FC07-45AF-902E-26787D28FF56@gmail.com> Message-ID: I tried that now. It wouldn't run `get-pip.py`. Says "Could not find a version that satisfies the requirement pip (from versions: ) No matching distribution found for pip" On Thu, Jun 11, 2015 at 10:14 PM, Phyo Arkar wrote: > It is just Download , extract , Run, and have fun. > > On Fri, Jun 12, 2015 at 1:43 AM, Phyo Arkar > wrote: > >> Have you tried portable pypy ? >> https://github.com/squeaky-pl/portable-pypy >> it works for me , in every linuxes. >> >> On Fri, Jun 12, 2015 at 1:42 AM, Ram Rachum wrote: >> >>> When you use the ppa, where will nosetests be located? >>> >>> On Thu, Jun 11, 2015 at 10:08 PM, Ryan Gonzalez >>> wrote: >>> >>>> sudo add-apt-repository ppa:pypy/ppa >>>> sudo apt-get update >>>> >>>> >>>> >>>> On June 11, 2015 1:54:55 PM CDT, Ram Rachum wrote: >>>>> >>>>> I have no idea how to use the PyPy PPA. (Not a Linux user here.) >>>>> >>>>> On Thu, Jun 11, 2015 at 9:52 PM, Randall Leeds < >>>>> randall.leeds at gmail.com> wrote: >>>>> >>>>>> The PyPy PPA works brilliantly on 15.04 for me. >>>>>> >>>>>> From there I just make a virtualenv with: >>>>>> >>>>>> $ virtualenv -P /usr/bin/pypy >>>>>> >>>>>> (Can't remember if it's -P or -p) >>>>>> >>>>>> Once activated, just running pip works fine for me. >>>>>> >>>>>> On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: >>>>>> >>>>>>> Against my better judgement, I tried following your advice :) >>>>>>> >>>>>>> Got this error when running make: >>>>>>> >>>>>>> [translation:ERROR] CompilationError: CompilationError(err=""" >>>>>>> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>>>>>> fatal error: zlib.h: No such file or directory >>>>>>> [translation:ERROR] #include >>>>>>> [translation:ERROR] ^ >>>>>>> [translation:ERROR] compilation terminated. >>>>>>> [translation:ERROR] """) >>>>>>> [translation] start debugger... >>>>>>> > >>>>>>> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>>>>>> -> raise last_error >>>>>>> (Pdb+) >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez >>>>>>> wrote: >>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Honestly, these is just general Linux issues. Like I said, not >>>>>>>>> even Linus Torvalds makes binaries of his dive logger for Linux. It a pain >>>>>>>>> in the everything. >>>>>>>>> >>>>>>>> >>>>>>>> *these are* (damn, I hate autocorrect...) >>>>>>>> >>>>>>>> >>>>>>>>> >>>>>>>>> I usually have the *worst* luck building stuff, but PyPy was >>>>>>>>> actually very easy. I ran `make` and it "just worked". You don't need to >>>>>>>>> know C. Even if you did, trying to edit the C code generated by RPython >>>>>>>>> would be suicide. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> I suck at building. I don't know C. There are likely to be errors >>>>>>>>>> that I wouldn't know how to deal with. I'm not interested in wasting >>>>>>>>>> another hour trying to deal with those. >>>>>>>>>> >>>>>>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>>>>>> >>>>>>>>>> Hopefully instead of investing so much development effort making >>>>>>>>>> PyPy x8 times faster than CPython instead of x7 faster, there'll be more >>>>>>>>>> effort to make PyPy easier to install. This also goes for Windows: Why >>>>>>>>>> isn't there an installer? But yeah, it's an open-source project, so I'm >>>>>>>>>> just ranting. >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> Remember: I am *dead* serious about you rebuilding it. If you're >>>>>>>>>>> on Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for >>>>>>>>>>> you to try. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum >>>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a >>>>>>>>>>>> message to python-ideas about this, maybe the -m flag should be changed to >>>>>>>>>>>> work on scripts. >>>>>>>>>>>> >>>>>>>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>>>>>>> given up at this point. Thanks for your help. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez < >>>>>>>>>>>> rymg19 at gmail.com> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that >>>>>>>>>>>>> works for some other Python packages. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>>>>>> @gmail.com> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> pypy -m pip works >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>>>>>>> something like this in my .bashr >>>>>>>>>>>>>>> c: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>>>>>> done >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> # Laziness >>>>>>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>>>>>> # it was either that or: >>>>>>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>>>>>> y-c" >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>>>>>>> windows). >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> * - >>>>>>>>>>>>>>>>>> How many hours of my life I need to spend to get PyPy to run. On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez > wrote: Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. On June 11, 2015 9:27:12 AM CDT, Ram Rachum > wrote: When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , how do I access the pip that belongs to PyPy?------------------------------ pypy-dev mai >>>>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>>>> list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity.------------------------------ pypy-dev mailing list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev * >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>>>>>> brevity. >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Ryan >>>>>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>>>>> your program. Something?s wrong. >>>>>>>>>>> http://kirbyfan64.github.io/ >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Ryan >>>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>>> your program. Something?s wrong. >>>>>>>>> http://kirbyfan64.github.io/ >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Ryan >>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>> your program. Something?s wrong. >>>>>>>> http://kirbyfan64.github.io/ >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> _______________________________________________ >>>>>>> pypy-dev mailing list >>>>>>> pypy-dev at python.org >>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>> >>>>>> >>>>> >>>> -- >>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>> >>> >>> >>> _______________________________________________ >>> pypy-dev mailing list >>> pypy-dev at python.org >>> https://mail.python.org/mailman/listinfo/pypy-dev >>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From phyo.arkarlwin at gmail.com Thu Jun 11 22:00:43 2015 From: phyo.arkarlwin at gmail.com (Phyo Arkar) Date: Fri, 12 Jun 2015 02:30:43 +0630 Subject: [pypy-dev] Question In-Reply-To: References: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> <968F7C54-FC07-45AF-902E-26787D28FF56@gmail.com> Message-ID: use easy_install On Fri, Jun 12, 2015 at 1:47 AM, Ram Rachum wrote: > I tried that now. It wouldn't run `get-pip.py`. Says "Could not find a > version that satisfies the requirement pip (from versions: ) > No matching distribution found for pip" > > On Thu, Jun 11, 2015 at 10:14 PM, Phyo Arkar > wrote: > >> It is just Download , extract , Run, and have fun. >> >> On Fri, Jun 12, 2015 at 1:43 AM, Phyo Arkar >> wrote: >> >>> Have you tried portable pypy ? >>> https://github.com/squeaky-pl/portable-pypy >>> it works for me , in every linuxes. >>> >>> On Fri, Jun 12, 2015 at 1:42 AM, Ram Rachum wrote: >>> >>>> When you use the ppa, where will nosetests be located? >>>> >>>> On Thu, Jun 11, 2015 at 10:08 PM, Ryan Gonzalez >>>> wrote: >>>> >>>>> sudo add-apt-repository ppa:pypy/ppa >>>>> sudo apt-get update >>>>> >>>>> >>>>> >>>>> On June 11, 2015 1:54:55 PM CDT, Ram Rachum wrote: >>>>>> >>>>>> I have no idea how to use the PyPy PPA. (Not a Linux user here.) >>>>>> >>>>>> On Thu, Jun 11, 2015 at 9:52 PM, Randall Leeds < >>>>>> randall.leeds at gmail.com> wrote: >>>>>> >>>>>>> The PyPy PPA works brilliantly on 15.04 for me. >>>>>>> >>>>>>> From there I just make a virtualenv with: >>>>>>> >>>>>>> $ virtualenv -P /usr/bin/pypy >>>>>>> >>>>>>> (Can't remember if it's -P or -p) >>>>>>> >>>>>>> Once activated, just running pip works fine for me. >>>>>>> >>>>>>> On Thu, Jun 11, 2015, 11:49 Ram Rachum wrote: >>>>>>> >>>>>>>> Against my better judgement, I tried following your advice :) >>>>>>>> >>>>>>>> Got this error when running make: >>>>>>>> >>>>>>>> [translation:ERROR] CompilationError: CompilationError(err=""" >>>>>>>> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>>>>>>> fatal error: zlib.h: No such file or directory >>>>>>>> [translation:ERROR] #include >>>>>>>> [translation:ERROR] ^ >>>>>>>> [translation:ERROR] compilation terminated. >>>>>>>> [translation:ERROR] """) >>>>>>>> [translation] start debugger... >>>>>>>> > >>>>>>>> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>>>>>>> -> raise last_error >>>>>>>> (Pdb+) >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez >>>>>>>> wrote: >>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Honestly, these is just general Linux issues. Like I said, not >>>>>>>>>> even Linus Torvalds makes binaries of his dive logger for Linux. It a pain >>>>>>>>>> in the everything. >>>>>>>>>> >>>>>>>>> >>>>>>>>> *these are* (damn, I hate autocorrect...) >>>>>>>>> >>>>>>>>> >>>>>>>>>> >>>>>>>>>> I usually have the *worst* luck building stuff, but PyPy was >>>>>>>>>> actually very easy. I ran `make` and it "just worked". You don't need to >>>>>>>>>> know C. Even if you did, trying to edit the C code generated by RPython >>>>>>>>>> would be suicide. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> I suck at building. I don't know C. There are likely to be >>>>>>>>>>> errors that I wouldn't know how to deal with. I'm not interested in wasting >>>>>>>>>>> another hour trying to deal with those. >>>>>>>>>>> >>>>>>>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>>>>>>> >>>>>>>>>>> Hopefully instead of investing so much development effort making >>>>>>>>>>> PyPy x8 times faster than CPython instead of x7 faster, there'll be more >>>>>>>>>>> effort to make PyPy easier to install. This also goes for Windows: Why >>>>>>>>>>> isn't there an installer? But yeah, it's an open-source project, so I'm >>>>>>>>>>> just ranting. >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>>>>>> > wrote: >>>>>>>>>>> >>>>>>>>>>>> Remember: I am *dead* serious about you rebuilding it. If >>>>>>>>>>>> you're on Ubuntu 14 LTS x64, I can email you the binaries I built that >>>>>>>>>>>> *work* for you to try. >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a >>>>>>>>>>>>> message to python-ideas about this, maybe the -m flag should be changed to >>>>>>>>>>>>> work on scripts. >>>>>>>>>>>>> >>>>>>>>>>>>> I tried a few things, including pyenv, but it didn't work. >>>>>>>>>>>>> I've given up at this point. Thanks for your help. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez < >>>>>>>>>>>>> rymg19 at gmail.com> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that >>>>>>>>>>>>>> works for some other Python packages. >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert < >>>>>>>>>>>>>> romain.py at gmail.com> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> pypy -m pip works >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>>>>>>>> something like this in my .bashr >>>>>>>>>>>>>>>> c: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>>>>>>> done >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> # Laziness >>>>>>>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>>>>>>> # it was either that or: >>>>>>>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>>>>>>> y-c" >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>>>>>>>> windows). >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> * - >>>>>>>>>>>>>>>>>>> How many hours of my life I need to spend to get PyPy to run. On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez > wrote: Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. On June 11, 2015 9:27:12 AM CDT, Ram Rachum > wrote: When I install Pypy on Ubuntu using apt-get, and then run get-pip.py , how do I access the pip that belongs to PyPy?------------------------------ pypy-dev mai >>>>>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>>>>> list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity.------------------------------ pypy-dev mailing list pypy-dev at python.org https://mail.python.org/mailman/listinfo/pypy-dev * >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>>>>>>> brevity. >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Ryan >>>>>>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>>>>>> your program. Something?s wrong. >>>>>>>>>>>> http://kirbyfan64.github.io/ >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Ryan >>>>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>>>> your program. Something?s wrong. >>>>>>>>>> http://kirbyfan64.github.io/ >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Ryan >>>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>>> your program. Something?s wrong. >>>>>>>>> http://kirbyfan64.github.io/ >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> pypy-dev mailing list >>>>>>>> pypy-dev at python.org >>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>> >>>>>>> >>>>>> >>>>> -- >>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>> >>>> >>>> >>>> _______________________________________________ >>>> pypy-dev mailing list >>>> pypy-dev at python.org >>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>> >>>> >>> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Thu Jun 11 23:08:16 2015 From: ram at rachum.com (Ram Rachum) Date: Fri, 12 Jun 2015 00:08:16 +0300 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: Using `make` worked. Thank you! On Thu, Jun 11, 2015 at 10:05 PM, Ram Rachum wrote: > Okay, I'll try it. (Once I add more resources to the VM so it could finish > faster.) > > On Thu, Jun 11, 2015 at 10:01 PM, Ryan Gonzalez wrote: > >> Ah, minor detail. You need to first run: >> >> sudo apt-get install libffi-dev pkg-config libz-dev libbz2-dev \ >> libsqlite3-dev libncurses-dev libexpat1-dev libssl-dev >> >> ;) >> >> >> On Thu, Jun 11, 2015 at 1:48 PM, Ram Rachum wrote: >> >>> Against my better judgement, I tried following your advice :) >>> >>> Got this error when running make: >>> >>> [translation:ERROR] CompilationError: CompilationError(err=""" >>> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>> fatal error: zlib.h: No such file or directory >>> [translation:ERROR] #include >>> [translation:ERROR] ^ >>> [translation:ERROR] compilation terminated. >>> [translation:ERROR] """) >>> [translation] start debugger... >>> > >>> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>> -> raise last_error >>> (Pdb+) >>> >>> >>> >>> >>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez wrote: >>> >>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>> wrote: >>>> >>>>> Honestly, these is just general Linux issues. Like I said, not even >>>>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>>>> the everything. >>>>> >>>> >>>> *these are* (damn, I hate autocorrect...) >>>> >>>> >>>>> >>>>> I usually have the *worst* luck building stuff, but PyPy was actually >>>>> very easy. I ran `make` and it "just worked". You don't need to know C. >>>>> Even if you did, trying to edit the C code generated by RPython would be >>>>> suicide. >>>>> >>>>> >>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>>>> >>>>>> I suck at building. I don't know C. There are likely to be errors >>>>>> that I wouldn't know how to deal with. I'm not interested in wasting >>>>>> another hour trying to deal with those. >>>>>> >>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>> >>>>>> Hopefully instead of investing so much development effort making PyPy >>>>>> x8 times faster than CPython instead of x7 faster, there'll be more effort >>>>>> to make PyPy easier to install. This also goes for Windows: Why isn't there >>>>>> an installer? But yeah, it's an open-source project, so I'm just ranting. >>>>>> >>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>> wrote: >>>>>> >>>>>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>>>>> to try. >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum wrote: >>>>>>> >>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a message to >>>>>>>> python-ideas about this, maybe the -m flag should be changed to work on >>>>>>>> scripts. >>>>>>>> >>>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>>> given up at this point. Thanks for your help. >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that works >>>>>>>>> for some other Python packages. >>>>>>>>> >>>>>>>>> >>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>> gmail.com> wrote: >>>>>>>>>> >>>>>>>>>> pypy -m pip works >>>>>>>>>> >>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>>> >>>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>>> something like this in my .bashrc: >>>>>>>>>>> >>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>> done >>>>>>>>>>> >>>>>>>>>>> # Laziness >>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>> # it was either that or: >>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>> y-c" >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>>> windows). >>>>>>>>>>>> >>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>> >>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>> >>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>>>>>> , >>>>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>> list >>>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>> >>>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>> >>>>>>>>>>> ------------------------------ >>>>>>>>>>> >>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> -- >>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>> brevity. >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Ryan >>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>>> program. Something?s wrong. >>>>>>> http://kirbyfan64.github.io/ >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan >>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>> program. Something?s wrong. >>>>> http://kirbyfan64.github.io/ >>>>> >>>>> >>>> >>>> >>>> >>>> -- >>>> Ryan >>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>> program. Something?s wrong. >>>> http://kirbyfan64.github.io/ >>>> >>>> >>> >>> >> >> >> -- >> Ryan >> [ERROR]: Your autotools build scripts are 200 lines longer than your >> program. Something?s wrong. >> http://kirbyfan64.github.io/ >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Thu Jun 11 23:10:32 2015 From: arigo at tunes.org (Armin Rigo) Date: Thu, 11 Jun 2015 23:10:32 +0200 Subject: [pypy-dev] Question In-Reply-To: References: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> <968F7C54-FC07-45AF-902E-26787D28FF56@gmail.com> Message-ID: Hi all, On 11 June 2015 at 21:17, Ram Rachum wrote: > I tried that now. It wouldn't run `get-pip.py`. Says "Could not find a > version that satisfies the requirement pip (from versions: ) > No matching distribution found for pip" My own experience: any PyPy binary can be downloaded from pypy.org/download.html for Ubuntu 64-bit (either the portable or the non-portable one; the latter works on Ubuntu from 12-04 to 14-04, so maybe also on 15-04). You unpack the tar, and then you use the system-provided "virtualenv" that you probably already have (at least the one on Ubuntu 14-04 works fine), like this: virtualenv -p /path/to/bin/pypy venv-pypy Then the usual instructions on how to use virtualenv work; for example, after running . venv-pypy/bin/activate then "python" becomes PyPy, "pip" is the one from venv-pypy, and "pip install foo" installs packages inside this venv-pypy directory. A bient?t, Armin. From rymg19 at gmail.com Thu Jun 11 23:59:21 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 16:59:21 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <2103DA02-B294-49E1-A4FE-9A12F24B56C3@gmail.com> <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: Told you so. :) On Thu, Jun 11, 2015 at 4:08 PM, Ram Rachum wrote: > Using `make` worked. Thank you! > > On Thu, Jun 11, 2015 at 10:05 PM, Ram Rachum wrote: > >> Okay, I'll try it. (Once I add more resources to the VM so it could >> finish faster.) >> >> On Thu, Jun 11, 2015 at 10:01 PM, Ryan Gonzalez wrote: >> >>> Ah, minor detail. You need to first run: >>> >>> sudo apt-get install libffi-dev pkg-config libz-dev libbz2-dev \ >>> libsqlite3-dev libncurses-dev libexpat1-dev libssl-dev >>> >>> ;) >>> >>> >>> On Thu, Jun 11, 2015 at 1:48 PM, Ram Rachum wrote: >>> >>>> Against my better judgement, I tried following your advice :) >>>> >>>> Got this error when running make: >>>> >>>> [translation:ERROR] CompilationError: CompilationError(err=""" >>>> [translation:ERROR] /tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>>> fatal error: zlib.h: No such file or directory >>>> [translation:ERROR] #include >>>> [translation:ERROR] ^ >>>> [translation:ERROR] compilation terminated. >>>> [translation:ERROR] """) >>>> [translation] start debugger... >>>> > >>>> /home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>>> -> raise last_error >>>> (Pdb+) >>>> >>>> >>>> >>>> >>>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez >>>> wrote: >>>> >>>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>>> wrote: >>>>> >>>>>> Honestly, these is just general Linux issues. Like I said, not even >>>>>> Linus Torvalds makes binaries of his dive logger for Linux. It a pain in >>>>>> the everything. >>>>>> >>>>> >>>>> *these are* (damn, I hate autocorrect...) >>>>> >>>>> >>>>>> >>>>>> I usually have the *worst* luck building stuff, but PyPy was actually >>>>>> very easy. I ran `make` and it "just worked". You don't need to know C. >>>>>> Even if you did, trying to edit the C code generated by RPython would be >>>>>> suicide. >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum wrote: >>>>>> >>>>>>> I suck at building. I don't know C. There are likely to be errors >>>>>>> that I wouldn't know how to deal with. I'm not interested in wasting >>>>>>> another hour trying to deal with those. >>>>>>> >>>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>>> >>>>>>> Hopefully instead of investing so much development effort making >>>>>>> PyPy x8 times faster than CPython instead of x7 faster, there'll be more >>>>>>> effort to make PyPy easier to install. This also goes for Windows: Why >>>>>>> isn't there an installer? But yeah, it's an open-source project, so I'm >>>>>>> just ranting. >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez >>>>>>> wrote: >>>>>>> >>>>>>>> Remember: I am *dead* serious about you rebuilding it. If you're on >>>>>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that *work* for you >>>>>>>> to try. >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a message >>>>>>>>> to python-ideas about this, maybe the -m flag should be changed to work on >>>>>>>>> scripts. >>>>>>>>> >>>>>>>>> I tried a few things, including pyenv, but it didn't work. I've >>>>>>>>> given up at this point. Thanks for your help. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that >>>>>>>>>> works for some other Python packages. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>>> gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>> pypy -m pip works >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez wrote: >>>>>>>>>>> >>>>>>>>>>>> I don't think you can out-of-the-box without some env tool. Blame apt-get's >>>>>>>>>>>> brilliant engineering. Since I'm generally allergic to binaries (I.e. THEY >>>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never distributes app binaries >>>>>>>>>>>> for Linux]), I do things the simple way: build it myself. Takes about 45 >>>>>>>>>>>> mins. Always works. pip and pytest and such will all get installed into the >>>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access them easily, I put >>>>>>>>>>>> something like this in my .bashrc: >>>>>>>>>>>> >>>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>>> done >>>>>>>>>>>> >>>>>>>>>>>> # Laziness >>>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>>> # it was either that or: >>>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>>> y-c" >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> As far as I know scripts don't get installed to site packages (at least on >>>>>>>>>>>>> windows). >>>>>>>>>>>>> >>>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose in it. I want to >>>>>>>>>>>>> launch the nosetests script. (I also have one for the system Python.) How do >>>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>>> >>>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed in >>>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>>> - How many hours of my life I need to spend to get PyPy to run. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely slow. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then run get-pip.py >>>>>>>>>>>>>>>>> , >>>>>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>>> list >>>>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my brevity. >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------ >>>>>>>>>>>> >>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>>> brevity. >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Ryan >>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >>>>>>>> your program. Something?s wrong. >>>>>>>> http://kirbyfan64.github.io/ >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ryan >>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>>> program. Something?s wrong. >>>>>> http://kirbyfan64.github.io/ >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan >>>>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>>>> program. Something?s wrong. >>>>> http://kirbyfan64.github.io/ >>>>> >>>>> >>>> >>>> >>> >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something?s wrong. >>> http://kirbyfan64.github.io/ >>> >>> >> >> > -- Ryan [ERROR]: Your autotools build scripts are 200 lines longer than your program. Something?s wrong. http://kirbyfan64.github.io/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Fri Jun 12 00:41:37 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Thu, 11 Jun 2015 17:41:37 -0500 Subject: [pypy-dev] Question In-Reply-To: References: <200D0A90-5022-4922-B6C4-65C89BFF0D82@gmail.com> <4B4424DD-18DD-4814-9CDC-4970A4266AD6@gmail.com> Message-ID: <5B9A0924-41CD-4C79-A370-F9C46E301A9E@gmail.com> Wait a sec...how the hell did it finish that quickly?? Takes ages for me... On June 11, 2015 4:08:16 PM CDT, Ram Rachum wrote: >Using `make` worked. Thank you! > >On Thu, Jun 11, 2015 at 10:05 PM, Ram Rachum wrote: > >> Okay, I'll try it. (Once I add more resources to the VM so it could >finish >> faster.) >> >> On Thu, Jun 11, 2015 at 10:01 PM, Ryan Gonzalez >wrote: >> >>> Ah, minor detail. You need to first run: >>> >>> sudo apt-get install libffi-dev pkg-config libz-dev libbz2-dev \ >>> libsqlite3-dev libncurses-dev libexpat1-dev libssl-dev >>> >>> ;) >>> >>> >>> On Thu, Jun 11, 2015 at 1:48 PM, Ram Rachum wrote: >>> >>>> Against my better judgement, I tried following your advice :) >>>> >>>> Got this error when running make: >>>> >>>> [translation:ERROR] CompilationError: CompilationError(err=""" >>>> [translation:ERROR] >/tmp/usession-release-2.6.0-0/platcheck_23.c:79:18: >>>> fatal error: zlib.h: No such file or directory >>>> [translation:ERROR] #include >>>> [translation:ERROR] ^ >>>> [translation:ERROR] compilation terminated. >>>> [translation:ERROR] """) >>>> [translation] start debugger... >>>> > >>>> >/home/ubuntu/Desktop/pypy-2.6.0-src/rpython/rtyper/tool/rffi_platform.py(834)configure_external_library() >>>> -> raise last_error >>>> (Pdb+) >>>> >>>> >>>> >>>> >>>> On Thu, Jun 11, 2015 at 9:43 PM, Ryan Gonzalez >wrote: >>>> >>>>> On Thu, Jun 11, 2015 at 1:39 PM, Ryan Gonzalez >>>>> wrote: >>>>> >>>>>> Honestly, these is just general Linux issues. Like I said, not >even >>>>>> Linus Torvalds makes binaries of his dive logger for Linux. It a >pain in >>>>>> the everything. >>>>>> >>>>> >>>>> *these are* (damn, I hate autocorrect...) >>>>> >>>>> >>>>>> >>>>>> I usually have the *worst* luck building stuff, but PyPy was >actually >>>>>> very easy. I ran `make` and it "just worked". You don't need to >know C. >>>>>> Even if you did, trying to edit the C code generated by RPython >would be >>>>>> suicide. >>>>>> >>>>>> >>>>>> On Thu, Jun 11, 2015 at 1:34 PM, Ram Rachum >wrote: >>>>>> >>>>>>> I suck at building. I don't know C. There are likely to be >errors >>>>>>> that I wouldn't know how to deal with. I'm not interested in >wasting >>>>>>> another hour trying to deal with those. >>>>>>> >>>>>>> I'm on Ubuntu 15.04. Thanks for the offer. >>>>>>> >>>>>>> Hopefully instead of investing so much development effort making >PyPy >>>>>>> x8 times faster than CPython instead of x7 faster, there'll be >more effort >>>>>>> to make PyPy easier to install. This also goes for Windows: Why >isn't there >>>>>>> an installer? But yeah, it's an open-source project, so I'm just >ranting. >>>>>>> >>>>>>> On Thu, Jun 11, 2015 at 9:30 PM, Ryan Gonzalez > >>>>>>> wrote: >>>>>>> >>>>>>>> Remember: I am *dead* serious about you rebuilding it. If >you're on >>>>>>>> Ubuntu 14 LTS x64, I can email you the binaries I built that >*work* for you >>>>>>>> to try. >>>>>>>> >>>>>>>> >>>>>>>> On Thu, Jun 11, 2015 at 12:52 PM, Ram Rachum >wrote: >>>>>>>> >>>>>>>>> Unfortunately it doesn't work for nosetests. I've sent a >message to >>>>>>>>> python-ideas about this, maybe the -m flag should be changed >to work on >>>>>>>>> scripts. >>>>>>>>> >>>>>>>>> I tried a few things, including pyenv, but it didn't work. >I've >>>>>>>>> given up at this point. Thanks for your help. >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Jun 11, 2015 at 8:15 PM, Ryan Gonzalez > >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Dang, I forgot about that. Unfortunately, I don't think that >works >>>>>>>>>> for some other Python packages. >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> On June 11, 2015 11:44:38 AM CDT, Romain Guillebert >>>>>>>>>> gmail.com> wrote: >>>>>>>>>>> >>>>>>>>>>> pypy -m pip works >>>>>>>>>>> >>>>>>>>>>> On Thu, Jun 11, 2015 at 5:05 PM, Ryan Gonzalez > wrote: >>>>>>>>>>> >>>>>>>>>>>> I don't think you can out-of-the-box without some env >tool. Blame apt-get's >>>>>>>>>>>> brilliant engineering. Since I'm generally allergic to >binaries (I.e. THEY >>>>>>>>>>>> DON'T WORK! [which is probably why Torvalds never >distributes app binaries >>>>>>>>>>>> for Linux]), I do things the simple way: build it myself. >Takes about 45 >>>>>>>>>>>> mins. Always works. pip and pytest and such will all get >installed into the >>>>>>>>>>>> source directory/bin, NOT /usr/local. In order to access >them easily, I put >>>>>>>>>>>> something like this in my .bashrc: >>>>>>>>>>>> >>>>>>>>>>>> for bin in $STUFF/pypy/bin; do >>>>>>>>>>>> alias pypy-${bin##*/}=$bin >>>>>>>>>>>> done >>>>>>>>>>>> >>>>>>>>>>>> # Laziness >>>>>>>>>>>> alias pypy="$STUFF/pypy/pypy-c" >>>>>>>>>>>> # it was either that or: >>>>>>>>>>>> alias pypy="$STUFF/pypy/bin/pyp >>>>>>>>>>>> y-c" >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> On June 11, 2015 10:00:50 AM CDT, Ram Rachum > wrote: >>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> As far as I know scripts don't get installed to site >packages (at least on >>>>>>>>>>>>> windows). >>>>>>>>>>>>> >>>>>>>>>>>>> In other words: say I installed pypy on Ubuntu with nose >in it. I want to >>>>>>>>>>>>> launch the nosetests script. (I also have one for the >system Python.) How do >>>>>>>>>>>>> I launch the nosetests that belongs to PyPy? >>>>>>>>>>>>> >>>>>>>>>>>>> On Jun 11, 2015 17:48, "Maciej Fijalkowski" > wrote: >>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> you can install pypy with apt-get. Stuff gets installed >in >>>>>>>>>>>>>> site-packages I believe (just like on cpython) >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 4:46 PM, Ram Rachum > wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Things I don't care about so much right now: >>>>>>>>>>>>>>> - How fast PyPy runs. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> Things I care a lot about right now: >>>>>>>>>>>>>>> - How many hours of my life I need to spend to get >PyPy to run. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> On Thu, Jun 11, 2015 at 5:36 PM, Ryan Gonzalez > >>>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Note: The PyPy bundled with Ubuntu 12 LTS is insanely >slow. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> On June 11, 2015 9:27:12 AM CDT, Ram Rachum > wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> When I install Pypy on Ubuntu using apt-get, and then >run get-pip.py >>>>>>>>>>>>>>>>> , >>>>>>>>>>>>>>>>> how do I access the pip that belongs to PyPy? >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> pypy-dev mai >>>>>>>>>>>>>>>>> ling >>>>>>>>>>>>>>>>> list >>>>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please >excuse my brevity. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> ------------------------------ >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse >my brevity. >>>>>>>>>>>> >>>>>>>>>>>> ------------------------------ >>>>>>>>>>>> >>>>>>>>>>>> pypy-dev mailing list >>>>>>>>>>>> pypy-dev at python.org >>>>>>>>>>>> https://mail.python.org/mailman/listinfo/pypy-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Sent from my Android device with K-9 Mail. Please excuse my >>>>>>>>>> brevity. >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> Ryan >>>>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >your >>>>>>>> program. Something?s wrong. >>>>>>>> http://kirbyfan64.github.io/ >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Ryan >>>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >your >>>>>> program. Something?s wrong. >>>>>> http://kirbyfan64.github.io/ >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Ryan >>>>> [ERROR]: Your autotools build scripts are 200 lines longer than >your >>>>> program. Something?s wrong. >>>>> http://kirbyfan64.github.io/ >>>>> >>>>> >>>> >>>> >>> >>> >>> -- >>> Ryan >>> [ERROR]: Your autotools build scripts are 200 lines longer than your >>> program. Something?s wrong. >>> http://kirbyfan64.github.io/ >>> >>> >> >> -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From cherian.rosh at gmail.com Sat Jun 13 03:48:58 2015 From: cherian.rosh at gmail.com (Roshan Cherian) Date: Fri, 12 Jun 2015 18:48:58 -0700 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors Message-ID: Hi All, I am building pypy 2.6.0 from source on a oel 6.3 with gcc: -bash-4.1$ gcc --version gcc (GCC) 4.4.6 20120305 (Red Hat 4.4.6-4) I am failing the compile_c task and doing a make: -bash-4.1$ make gcc -O3 -pthread -fomit-frame-pointer -Wall -Wno-unused -I/tmp/pypy260/lib/libffi-3.0.13/include -O3 -g -fPIC -fPIC -fvisibility=hidden -DPy_BUILD_CORE -DPYPY_USE_ASMGCC -DPYPY_JIT_CODEMAP -DPYPY_CPU_HAS_STANDARD_PRECISION -DPy_BUILD_CORE -frandom-seed=testing_1.c -o testing_1.s -S testing_1.c -I"/home/roshan/python/pypy-2.6.0/rpython"/translator/c -I/home/roshan/python/pypy-2.6.0/pypy/module/cpyext/include -I.. -I/home/roshan/python/pypy-2.6.0/pypy/module/_vmprof/src -I/home/roshan/python/pypy-2.6.0/pypy/module/_cffi_backend/src -I/home/roshan/python/pypy-2.6.0/pypy/module/_multibytecodec -I/home/roshan/python/pypy-2.6.0/pypy/module/operator -I/tmp/pypy260/lib/libffi-3.0.13/include In file included from testing_1.c:4: forwarddecl.h:94137: error: expected declaration specifiers or ?...? before ?EC_KEY? In file included from testing_1.c:4: forwarddecl.h:131517: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?*? token forwarddecl.h:131518: error: expected ?)? before ?*? token forwarddecl.h:131520: error: expected declaration specifiers or ?...? before ?EC_KEY? In file included from testing_1.c:4: forwarddecl.h:155867: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?*? token make: *** [testing_1.gcmap] Error 1 Could you please help? Thanks, -Roshan -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Sat Jun 13 08:58:34 2015 From: arigo at tunes.org (Armin Rigo) Date: Sat, 13 Jun 2015 08:58:34 +0200 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: References: Message-ID: Hi Roshan, On 13 June 2015 at 03:48, Roshan Cherian wrote: > In file included from testing_1.c:4: > > forwarddecl.h:94137: error: expected declaration specifiers or ?...? before > ?EC_KEY? My guess is that you didn't show us the complete output. The first error message you got should be about not finding some #include. It's probably pointing to or something similar. Make sure you install the dependencies: http://pypy.readthedocs.org/en/latest/build.html#install-build-time-dependencies A bient?t, Armin. From arigo at tunes.org Sat Jun 13 09:01:28 2015 From: arigo at tunes.org (Armin Rigo) Date: Sat, 13 Jun 2015 09:01:28 +0200 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> Message-ID: Hi Ram, On 11 June 2015 at 16:28, Ram Rachum wrote: > Didn't work. All we can do is repeat the instructions. Try following them exactly, at first: - assuming you have downloaded pypy-c-jit-X.tar.bz2, for some value of X - run: tar jxf pypy-c-jit-X.tar.bz2 - cd pypy-c-jit-X/bin - ./pypy A bient?t, Armin. From arigo at tunes.org Sat Jun 13 09:09:25 2015 From: arigo at tunes.org (Armin Rigo) Date: Sat, 13 Jun 2015 09:09:25 +0200 Subject: [pypy-dev] Freezing the ".pypy-26.so" name? Message-ID: Hi all, The cpyext and cffi extension modules are created with the extension ".pypy-XY.so", were X and Y are the current PyPy version. I believe that there is little point any more: as far as I'm aware, nothing in the API changed since a long time, and all these different versions are identical to each other. Should we simply freeze the ".pypy-26.so" name, so that future PyPy's will also use it, at least until some really incompatible change is made? This would resolve for example issues like https://github.com/pypa/pip/issues/2882 . A bient?t, Armin. From donald at stufft.io Sat Jun 13 09:13:35 2015 From: donald at stufft.io (Donald Stufft) Date: Sat, 13 Jun 2015 03:13:35 -0400 Subject: [pypy-dev] Freezing the ".pypy-26.so" name? In-Reply-To: References: Message-ID: On June 13, 2015 at 3:10:39 AM, Armin Rigo (arigo at tunes.org) wrote: > Hi all, > > The cpyext and cffi extension modules are created with the extension > ".pypy-XY.so", were X and Y are the current PyPy version. I believe > that there is little point any more: as far as I'm aware, nothing in > the API changed since a long time, and all these different versions > are identical to each other. Should we simply freeze the > ".pypy-26.so" name, so that future PyPy's will also use it, at least > until some really incompatible change is made? > > This would resolve for example issues like > https://github.com/pypa/pip/issues/2882 . > > > A bient?t, > > Armin. > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > For the uses of pip, it would be preferable if there was an exported stable ABI that we could leverage to tag wheels with. For the people *making* Wheels, the less often that stable ABI changed the better, since a single wheel would be useful for more versions of PyPy then. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA From arigo at tunes.org Sat Jun 13 09:22:38 2015 From: arigo at tunes.org (Armin Rigo) Date: Sat, 13 Jun 2015 09:22:38 +0200 Subject: [pypy-dev] Freezing the ".pypy-26.so" name? In-Reply-To: References: Message-ID: Hi Donald, On 13 June 2015 at 09:13, Donald Stufft wrote: > For the uses of pip, it would be preferable if there was an exported stable ABI > that we could leverage to tag wheels with. For the people *making* Wheels, the > less often that stable ABI changed the better, since a single wheel would be > useful for more versions of PyPy then. Sorry, I meant that nothing changed in the ABI, in addition to the API. You can just rename an existing "foo.pypy-25.so" to "foo.pypy-26.so" and it should work. Note that you have to assume that I don't know the problems related to making wheels, and give some more details in your answer. I'm ready to hear about any suggestion if fixing "imp.get_suffixes()" is either not a good idea, or ok but the same information needs to be exported some other way too. The point is that using sys.version_info[:2] is too vague, given that it is always (2, 7), and using sys.pypy_version_info[:2] is (or will become) too precise. A bient?t, Armin. From donald at stufft.io Sat Jun 13 09:31:04 2015 From: donald at stufft.io (Donald Stufft) Date: Sat, 13 Jun 2015 03:31:04 -0400 Subject: [pypy-dev] Freezing the ".pypy-26.so" name? In-Reply-To: References: Message-ID: On June 13, 2015 at 3:23:21 AM, Armin Rigo (arigo at tunes.org) wrote: > Hi Donald, > > On 13 June 2015 at 09:13, Donald Stufft wrote: > > For the uses of pip, it would be preferable if there was an exported stable ABI > > that we could leverage to tag wheels with. For the people *making* Wheels, the > > less often that stable ABI changed the better, since a single wheel would be > > useful for more versions of PyPy then. > > Sorry, I meant that nothing changed in the ABI, in addition to the > API. You can just rename an existing "foo.pypy-25.so" to > "foo.pypy-26.so" and it should work. > > Note that you have to assume that I don't know the problems related to > making wheels, and give some more details in your answer. I'm ready > to hear about any suggestion if fixing "imp.get_suffixes()" is either > not a good idea, or ok but the same information needs to be exported > some other way too. The point is that using sys.version_info[:2] is > too vague, given that it is always (2, 7), and using > sys.pypy_version_info[:2] is (or will become) too precise. > > > A bient?t, > > Armin. > Sorry, to be clear, I wasn't saying your idea was bad. I was just making it clear that whatever it is should reflect the actual ABI of the module. So if there are compile options (does JIT vs not change it?) then that should be reflected in it too. Ideally it'd contain enough information to know if something compiled for a particular PyPy is ABI compatible with another one. As far as how it's exported, the suffixes is a good starting place, and if the ABI tag can also be added to sysconfig.get_config_var("SOABI") that would be good too. For example, CPython (in the 3.x branch) has:: ? ? >>> import sysconfig ? ? >>> sysconfig.get_config_var("SOABI") ? ? 'cpython-34m' This is a CPython 3.4 compiled with --with-pymalloc. The CPython bits are here: https://www.python.org/dev/peps/pep-3149/ Generally though, I'm +1 on starting to define an actual ABI (and not breaking it without updating the tag to reflect that). As far as wheels goes, the important thing is that we'll make the SOABI part of the wheel filename and use it to select which wheel we'll download and install. You don't need to worry about that much other than the fact that defining one makes it better and being conservative in changing it makes it better. --- Donald Stufft PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA From ram at rachum.com Sat Jun 13 10:06:06 2015 From: ram at rachum.com (Ram Rachum) Date: Sat, 13 Jun 2015 11:06:06 +0300 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> Message-ID: Hello Armin, I already said I tried it 3 days ago and showed you the error I got, I'm not sure why you're assuming I haven't followed the instructions correctly. Is it so hard to believe that PyPy has a bug or the instructions need tweaking? (BTW your instructions weren't precise, the file to run is pypy3.) Here's my shell session trying your instructions: root at ubuntu:/home/ubuntu/Desktop# curl -O http://buildbot.pypy.org/nightly/py3.3/pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 19.7M 100 19.7M 0 0 458k 0 0:00:44 0:00:44 --:--:-- 674k root at ubuntu:/home/ubuntu/Desktop# tar jxf pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 root at ubuntu:/home/ubuntu/Desktop# cd pypy-c-jit-76553-deae634f291c-linux64/bin/ root at ubuntu:/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# ./pypy bash: ./pypy: No such file or directory root at ubuntu:/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# ./pypy3 debug: OperationError: debug: operror-type: ImportError debug: operror-value: No module named 'encodings' debug: OperationError: debug: operror-type: AttributeError debug: operror-value: stdout root at ubuntu:/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# On Sat, Jun 13, 2015 at 10:01 AM, Armin Rigo wrote: > Hi Ram, > > On 11 June 2015 at 16:28, Ram Rachum wrote: > > Didn't work. > > All we can do is repeat the instructions. Try following them exactly, at > first: > > - assuming you have downloaded pypy-c-jit-X.tar.bz2, for some value of X > > - run: tar jxf pypy-c-jit-X.tar.bz2 > > - cd pypy-c-jit-X/bin > > - ./pypy > > > A bient?t, > > Armin. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Sat Jun 13 10:20:29 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Sat, 13 Jun 2015 10:20:29 +0200 Subject: [pypy-dev] Freezing the ".pypy-26.so" name? In-Reply-To: References: Message-ID: 2015-06-13 9:31 GMT+02:00 Donald Stufft : > > > On June 13, 2015 at 3:23:21 AM, Armin Rigo (arigo at tunes.org) wrote: > > Hi Donald, > > > > On 13 June 2015 at 09:13, Donald Stufft wrote: > > > For the uses of pip, it would be preferable if there was an exported > stable ABI > > > that we could leverage to tag wheels with. For the people *making* > Wheels, the > > > less often that stable ABI changed the better, since a single wheel > would be > > > useful for more versions of PyPy then. > > > > Sorry, I meant that nothing changed in the ABI, in addition to the > > API. You can just rename an existing "foo.pypy-25.so" to > > "foo.pypy-26.so" and it should work. > > > > Note that you have to assume that I don't know the problems related to > > making wheels, and give some more details in your answer. I'm ready > > to hear about any suggestion if fixing "imp.get_suffixes()" is either > > not a good idea, or ok but the same information needs to be exported > > some other way too. The point is that using sys.version_info[:2] is > > too vague, given that it is always (2, 7), and using > > sys.pypy_version_info[:2] is (or will become) too precise. > > > > > > A bient?t, > > > > Armin. > > > > Sorry, to be clear, I wasn't saying your idea was bad. I was just making it > clear that whatever it is should reflect the actual ABI of the module. So > if > there are compile options (does JIT vs not change it?) then that should be > reflected in it too. Ideally it'd contain enough information to know if > something compiled for a particular PyPy is ABI compatible with another > one. > But cffi extension modules are not real modules, right? When compiled for PyPy, the init function has a different name, and fills a C struct that cannot be considered as a Python module. They can be imported only because there is special support in the import framework. In this case, why not have a completely different extension or SOABI? Like _sqlite.cffi1.0.so > > As far as how it's exported, the suffixes is a good starting place, and if > the > ABI tag can also be added to sysconfig.get_config_var("SOABI") that would > be > good too. > > For example, CPython (in the 3.x branch) has:: > > >>> import sysconfig > >>> sysconfig.get_config_var("SOABI") > 'cpython-34m' > > This is a CPython 3.4 compiled with --with-pymalloc. The CPython bits are > here: https://www.python.org/dev/peps/pep-3149/ > > Generally though, I'm +1 on starting to define an actual ABI (and not > breaking > it without updating the tag to reflect that). As far as wheels goes, the > important thing is that we'll make the SOABI part of the wheel filename > and use > it to select which wheel we'll download and install. You don't need to > worry > about that much other than the fact that defining one makes it better and > being conservative in changing it makes it better. > > --- > Donald Stufft > PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Sat Jun 13 10:50:24 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Sat, 13 Jun 2015 10:50:24 +0200 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> Message-ID: 2015-06-13 10:06 GMT+02:00 Ram Rachum : > Hello Armin, > > I already said I tried it 3 days ago and showed you the error I got, I'm > not sure why you're assuming I haven't followed the instructions correctly. > Is it so hard to believe that PyPy has a bug or the instructions need > tweaking? (BTW your instructions weren't precise, the file to run is pypy3.) > > Here's my shell session trying your instructions: > > root at ubuntu:/home/ubuntu/Desktop# curl -O > http://buildbot.pypy.org/nightly/py3.3/pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 19.7M 100 19.7M 0 0 458k 0 0:00:44 0:00:44 --:--:-- > 674k > root at ubuntu:/home/ubuntu/Desktop# tar jxf > pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 > root at ubuntu:/home/ubuntu/Desktop# cd > pypy-c-jit-76553-deae634f291c-linux64/bin/ > root at ubuntu:/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# > ./pypy > bash: ./pypy: No such file or directory > root at ubuntu:/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# > ./pypy3 > debug: OperationError: > debug: operror-type: ImportError > debug: operror-value: No module named 'encodings' > debug: OperationError: > debug: operror-type: AttributeError > debug: operror-value: stdout > root at ubuntu > :/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# > > Can you try with LANG=C ./pypy3 And if it does, what's the value of LANG in your environment? > > > > On Sat, Jun 13, 2015 at 10:01 AM, Armin Rigo wrote: > >> Hi Ram, >> >> On 11 June 2015 at 16:28, Ram Rachum wrote: >> > Didn't work. >> >> All we can do is repeat the instructions. Try following them exactly, at >> first: >> >> - assuming you have downloaded pypy-c-jit-X.tar.bz2, for some value of X >> >> - run: tar jxf pypy-c-jit-X.tar.bz2 >> >> - cd pypy-c-jit-X/bin >> >> - ./pypy >> >> >> A bient?t, >> >> Armin. >> > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Sat Jun 13 10:53:53 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Sat, 13 Jun 2015 10:53:53 +0200 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> Message-ID: Sorry, forget what I said. There is a big issue with the archive file, most stdlib files are missing. 2015-06-13 10:50 GMT+02:00 Amaury Forgeot d'Arc : > 2015-06-13 10:06 GMT+02:00 Ram Rachum : > >> Hello Armin, >> >> I already said I tried it 3 days ago and showed you the error I got, I'm >> not sure why you're assuming I haven't followed the instructions correctly. >> Is it so hard to believe that PyPy has a bug or the instructions need >> tweaking? (BTW your instructions weren't precise, the file to run is pypy3.) >> >> Here's my shell session trying your instructions: >> >> root at ubuntu:/home/ubuntu/Desktop# curl -O >> http://buildbot.pypy.org/nightly/py3.3/pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 >> % Total % Received % Xferd Average Speed Time Time Time >> Current >> Dload Upload Total Spent Left >> Speed >> 100 19.7M 100 19.7M 0 0 458k 0 0:00:44 0:00:44 --:--:-- >> 674k >> root at ubuntu:/home/ubuntu/Desktop# tar jxf >> pypy-c-jit-76553-deae634f291c-linux64.tar.bz2 >> root at ubuntu:/home/ubuntu/Desktop# cd >> pypy-c-jit-76553-deae634f291c-linux64/bin/ >> root at ubuntu:/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# >> ./pypy >> bash: ./pypy: No such file or directory >> root at ubuntu:/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# >> ./pypy3 >> debug: OperationError: >> debug: operror-type: ImportError >> debug: operror-value: No module named 'encodings' >> debug: OperationError: >> debug: operror-type: AttributeError >> debug: operror-value: stdout >> root at ubuntu >> :/home/ubuntu/Desktop/pypy-c-jit-76553-deae634f291c-linux64/bin# >> >> > Can you try with > LANG=C ./pypy3 > > And if it does, what's the value of LANG in your environment? > > > >> >> >> >> On Sat, Jun 13, 2015 at 10:01 AM, Armin Rigo wrote: >> >>> Hi Ram, >>> >>> On 11 June 2015 at 16:28, Ram Rachum wrote: >>> > Didn't work. >>> >>> All we can do is repeat the instructions. Try following them exactly, >>> at first: >>> >>> - assuming you have downloaded pypy-c-jit-X.tar.bz2, for some value of X >>> >>> - run: tar jxf pypy-c-jit-X.tar.bz2 >>> >>> - cd pypy-c-jit-X/bin >>> >>> - ./pypy >>> >>> >>> A bient?t, >>> >>> Armin. >>> >> >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> >> > > > -- > Amaury Forgeot d'Arc > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From yury at shurup.com Sat Jun 13 11:14:18 2015 From: yury at shurup.com (Yury V. Zaytsev) Date: Sat, 13 Jun 2015 11:14:18 +0200 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: References: Message-ID: <1434186858.2899.395.camel@newpride> On Sat, 2015-06-13 at 08:58 +0200, Armin Rigo wrote: > My guess is that you didn't show us the complete output. Isn't gcc 4.4 way too old anyways? FYI, one can get newer gcc on OEL 6 from Software Collections / DevToolset. -- Sincerely yours, Yury V. Zaytsev From cherian.rosh at gmail.com Sat Jun 13 21:22:29 2015 From: cherian.rosh at gmail.com (Roshan Cherian) Date: Sat, 13 Jun 2015 12:22:29 -0700 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: <1434186858.2899.395.camel@newpride> References: <1434186858.2899.395.camel@newpride> Message-ID: Hi Yuri and Armin, Thanks for the response. Our build system uses gcc 4.4.6 as a result I am kind of confined to it. I am copying the part which has lead to the error. Please let me know how I can provide more info. Thanks for your help, -Roshan [c:writing] rpython_rlib_rweaklist.c [c:writing] rpython_rlib_rzipfile.c [c:writing] rpython_rlib_rzlib.c [c:writing] rpython_rlib_special_value.c [c:writing] rpython_rlib_streamio.c [c:writing] rpython_rlib_unicodedata_unicodedb_3_2_0.c [c:writing] rpython_rlib_unicodedata_unicodedb_5_2_0.c [c:writing] rpython_rtyper_lltypesystem_ll_str.c [c:writing] rpython_rtyper_lltypesystem_lltype.c [c:writing] rpython_rtyper_lltypesystem_module_ll_math.c [c:writing] rpython_rtyper_lltypesystem_rbuilder.c [c:writing] rpython_rtyper_lltypesystem_rdict.c [c:writing] rpython_rtyper_lltypesystem_rffi.c [c:writing] rpython_rtyper_lltypesystem_rlist.c [c:writing] rpython_rtyper_lltypesystem_rordereddict.c [c:writing] rpython_rtyper_lltypesystem_rordereddict_1.c [c:writing] rpython_rtyper_lltypesystem_rordereddict_2.c [c:writing] rpython_rtyper_lltypesystem_rordereddict_3.c [c:writing] rpython_rtyper_lltypesystem_rordereddict_4.c [c:writing] rpython_rtyper_lltypesystem_rordereddict_5.c [c:writing] rpython_rtyper_lltypesystem_rstr.c [c:writing] rpython_rtyper_module_ll_os.c [c:writing] rpython_rtyper_module_ll_os_environ.c [c:writing] rpython_rtyper_module_ll_os_stat.c [c:writing] rpython_rtyper_module_ll_time.c [c:writing] rpython_rtyper_rclass.c [c:writing] rpython_rtyper_rfloat.c [c:writing] rpython_rtyper_rint.c [c:writing] rpython_rtyper_rlist.c [c:writing] rpython_rtyper_rrange.c [c:writing] rpython_rtyper_rstr.c [c:writing] rpython_tool_error.c [c:writing] rpython_translator_c_extfunc.c [c:writing] rpython_translator_exceptiontransform.c [translation:info] written: /tmp/usession-release-2.6.0-4/testing_1/testing_1.c [4d2eb] translation-task} [translation:info] Compiling c source... [4d2eb] {translation-task starting compile_c [platform:execute] make in /tmp/usession-release-2.6.0-4/testing_1 [platform:Error] In file included from testing_1.c:4: [platform:Error] forwarddecl.h:94149: error: expected declaration specifiers or ?...? before ?EC_KEY? [platform:Error] In file included from testing_1.c:4: [platform:Error] forwarddecl.h:131540: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?*? token [platform:Error] forwarddecl.h:131541: error: expected ?)? before ?*? token [platform:Error] forwarddecl.h:131543: error: expected declaration specifiers or ?...? before ?EC_KEY? [platform:Error] In file included from testing_1.c:4: [platform:Error] forwarddecl.h:155882: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?*? token [platform:Error] make: *** [testing_1.gcmap] Error 1 [4d2eb] translation-task} [Timer] Timings: [Timer] annotate --- 565.2 s [Timer] rtype_lltype --- 704.7 s [Timer] pyjitpl_lltype --- 1005.1 s [Timer] backendopt_lltype --- 189.4 s [Timer] stackcheckinsertion_lltype --- 93.6 s [Timer] database_c --- 304.3 s [Timer] source_c --- 352.4 s [Timer] compile_c --- 2.9 s [Timer] =========================================== [Timer] Total: --- 3217.6 s [translation:info] Error: [translation:info] File "/home/roshan/python/pypy-2.6.0/rpython/translator/goal/translate.py", line 318, in main [translation:info] drv.proceed(goals) [translation:info] File "/home/roshan/python/pypy-2.6.0/rpython/translator/driver.py", line 549, in proceed [translation:info] return self._execute(goals, task_skip = self._maybe_skip()) [translation:info] File "/home/roshan/python/pypy-2.6.0/rpython/translator/tool/taskengine.py", line 114, in _execute [translation:info] res = self._do(goal, taskcallable, *args, **kwds) [translation:info] File "/home/roshan/python/pypy-2.6.0/rpython/translator/driver.py", line 277, in _do [translation:info] res = func() [translation:info] File "/home/roshan/python/pypy-2.6.0/rpython/translator/driver.py", line 515, in task_compile_c [translation:info] cbuilder.compile(**kwds) [translation:info] File "/home/roshan/python/pypy-2.6.0/rpython/translator/c/genc.py", line 376, in compile [translation:info] extra_opts) [translation:info] File "/home/roshan/python/pypy-2.6.0/rpython/translator/platform/posix.py", line 211, in execute_makefile [translation:info] self._handle_error(returncode, stdout, stderr, path.join('make')) [translation:info] File "/home/roshan/python/pypy-2.6.0/rpython/translator/platform/__init__.py", line 151, in _handle_error [translation:info] raise CompilationError(stdout, stderr) [translation:ERROR] CompilationError: CompilationError(err=""" [translation:ERROR] In file included from testing_1.c:4: [translation:ERROR] forwarddecl.h:94149: error: expected declaration specifiers or ?...? before ?EC_KEY? [translation:ERROR] In file included from testing_1.c:4: [translation:ERROR] forwarddecl.h:131540: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?*? token [translation:ERROR] forwarddecl.h:131541: error: expected ?)? before ?*? token [translation:ERROR] forwarddecl.h:131543: error: expected declaration specifiers or ?...? before ?EC_KEY? [translation:ERROR] In file included from testing_1.c:4: [translation:ERROR] forwarddecl.h:155882: error: expected ?=?, ?,?, ?;?, ?asm? or ?__attribute__? before ?*? token [translation:ERROR] make: *** [testing_1.gcmap] Error 1 [translation:ERROR] """) [translation] start debugger... > /home/roshan/python/pypy-2.6.0/rpython/translator/platform/__init__.py(151)_handle_error() -> raise CompilationError(stdout, stderr) On Sat, Jun 13, 2015 at 2:14 AM, Yury V. Zaytsev wrote: > On Sat, 2015-06-13 at 08:58 +0200, Armin Rigo wrote: > > My guess is that you didn't show us the complete output. > > Isn't gcc 4.4 way too old anyways? FYI, one can get newer gcc on OEL 6 > from Software Collections / DevToolset. > > -- > Sincerely yours, > Yury V. Zaytsev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Sun Jun 14 14:21:57 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 14 Jun 2015 14:21:57 +0200 Subject: [pypy-dev] Freezing the ".pypy-26.so" name? In-Reply-To: References: Message-ID: Hi Amaury, On 13 June 2015 at 10:20, Amaury Forgeot d'Arc wrote: > But cffi extension modules are not real modules, right? > When compiled for PyPy, the init function has a different name, and fills a > C struct that cannot be considered as a Python module. > > They can be imported only because there is special support in the import > framework. > > In this case, why not have a completely different extension or SOABI? > Like _sqlite.cffi1.0.so They are "real" modules in the sense that the .c file is exactly the same as for CPython, and they are compiled with the same unmodifed distutils. They are not "real" only in the sense that there are some "#ifdef PYPY_VERSION" which end up not making use of any of the Python.h functions and exporting a differently-named init function. That's why, so far, I didn't bother trying to convince distutils that it should give different extensions for CPython C extension modules and for CFFI modules. We could try to call them _sqlite.cffi1.0.so, or even have .so's compiled for CPython 2.7 be directly importable under PyPy2 (by always exporting both variants of the init function). This requires hacks to distutils which I'm not comfortable with. At least the current solution has one standard SOABI, namely ".pypy-26.so", rather than trying to export two of them and confuse the other tools that depend on distutils (setuptools, pip...). A bient?t, Armin. From arigo at tunes.org Sun Jun 14 14:48:51 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 14 Jun 2015 14:48:51 +0200 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> Message-ID: Hi Ram, On 13 June 2015 at 10:06, Ram Rachum wrote: > I already said I tried it 3 days ago and showed you the error I got, I'm not > sure why you're assuming I haven't followed the instructions correctly. Is > it so hard to believe that PyPy has a bug or the instructions need tweaking? > (BTW your instructions weren't precise, the file to run is pypy3.) Oh, I'm sorry. I got confused and forgot that you're asking about pypy3 specifically. These instructions are working for pypy2. It is why I thought you did something more, like copy the binary around somewhere else, and so I asked you to follow these steps exactly. But it doesn't work with pypy3, so it's a bug. Armin From arigo at tunes.org Sun Jun 14 14:54:28 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 14 Jun 2015 14:54:28 +0200 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: References: <1434186858.2899.395.camel@newpride> Message-ID: Hi Roshan, On 13 June 2015 at 21:22, Roshan Cherian wrote: > Our build system uses gcc 4.4.6 as a result I am kind of confined to it. I > am copying the part which has lead to the error. Please let me know how I > can provide more info. Maybe you have an old version of openssl installed, too? One which would not define the type 'EC_KEY'. Try to grep for 'EC_KEY' in '/usr/include/openssl/*.h'. A bient?t, Armin. From ram at rachum.com Sun Jun 14 15:00:52 2015 From: ram at rachum.com (Ram Rachum) Date: Sun, 14 Jun 2015 16:00:52 +0300 Subject: [pypy-dev] Working version of pypy3 that support Python 3.3 In-Reply-To: References: <56A658BB-B03D-4CE0-A6E0-1E5F8F6F5868@gmail.com> Message-ID: That's cool :) On Sun, Jun 14, 2015 at 3:48 PM, Armin Rigo wrote: > Hi Ram, > > On 13 June 2015 at 10:06, Ram Rachum wrote: > > I already said I tried it 3 days ago and showed you the error I got, I'm > not > > sure why you're assuming I haven't followed the instructions correctly. > Is > > it so hard to believe that PyPy has a bug or the instructions need > tweaking? > > (BTW your instructions weren't precise, the file to run is pypy3.) > > Oh, I'm sorry. I got confused and forgot that you're asking about > pypy3 specifically. These instructions are working for pypy2. It is > why I thought you did something more, like copy the binary around > somewhere else, and so I asked you to follow these steps exactly. But > it doesn't work with pypy3, so it's a bug. > > Armin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Sun Jun 14 15:01:42 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 14 Jun 2015 15:01:42 +0200 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: References: <1434186858.2899.395.camel@newpride> Message-ID: Re-hi, On 14 June 2015 at 14:54, Armin Rigo wrote: > Maybe you have an old version of openssl installed, too? One which > would not define the type 'EC_KEY'. Try to grep for 'EC_KEY' in > '/usr/include/openssl/*.h'. Another way in which a different version of openssl might create this confusion: on my machine, EC_KEY is defined in openssl/ec.h, but we don't explicitly include this file. So try to add ``#include "openssl/ec.h"`` to the end of the generated file ``common_header.h``. If it helps, then it's indeed the source of the problem, and it can be definitely fixed by editing rpython/rlib/ropenssl.py and adding a line to the ``includes += [``. A bient?t, Armin. From lac at openend.se Sun Jun 14 16:56:07 2015 From: lac at openend.se (Laura Creighton) Date: Sun, 14 Jun 2015 16:56:07 +0200 Subject: [pypy-dev] Freezing the ".pypy-26.so" name? In-Reply-To: Message from Armin Rigo of "Sun, 14 Jun 2015 14:21:57 +0200." References: Message-ID: <201506141456.t5EEu7aT018809@fido.openend.se> I think that we had better look at wheels. I only thought it was a better egg, which since I never thought eggs were a good idea, I didn't worry about. But looks like I was wrong. I only started to look at them yesterday, so I am likely full of nonsense but looks like we could make a wheel that doesn't need distutils. Which I still only have found the idea of, and not the code of, which I want to look at. People who find relevant code, please mail me where this is. Laura From amauryfa at gmail.com Sun Jun 14 21:38:18 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Sun, 14 Jun 2015 21:38:18 +0200 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: References: <1434186858.2899.395.camel@newpride> Message-ID: 2015-06-14 14:54 GMT+02:00 Armin Rigo : > Hi Roshan, > > On 13 June 2015 at 21:22, Roshan Cherian wrote: > > Our build system uses gcc 4.4.6 as a result I am kind of confined to it. > I > > am copying the part which has lead to the error. Please let me know how I > > can provide more info. > > Maybe you have an old version of openssl installed, too? One which > would not define the type 'EC_KEY'. Try to grep for 'EC_KEY' in > '/usr/include/openssl/*.h'. > Or this installation of openssl is built with "OPENSSL_NO_ECDH". CPython respects this flag, PyPy does not. -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Mon Jun 15 07:49:20 2015 From: ram at rachum.com (Ram Rachum) Date: Mon, 15 Jun 2015 08:49:20 +0300 Subject: [pypy-dev] Heroku PyPy buildpack Message-ID: If I want to use a modern version of PyPy on Heroku (they currently only allow PyPy 1.9 by default,) did someone make a Heroku buildpack with a recent PyPy? That'll make it easy for many people to start using PyPy for their web apps. -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Mon Jun 15 08:46:19 2015 From: arigo at tunes.org (Armin Rigo) Date: Mon, 15 Jun 2015 08:46:19 +0200 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: References: <1434186858.2899.395.camel@newpride> Message-ID: Hi Roshan, On 14 June 2015 at 21:38, Amaury Forgeot d'Arc wrote: > Or this installation of openssl is built with "OPENSSL_NO_ECDH". > CPython respects this flag, PyPy does not. If someone could check if that's the case, please open an issue then (http://bugs.pypy.org/). Armin From samo at meluria.com Mon Jun 15 20:59:27 2015 From: samo at meluria.com (Samuel Villamonte) Date: Mon, 15 Jun 2015 13:59:27 -0500 Subject: [pypy-dev] Heroku PyPy buildpack In-Reply-To: References: Message-ID: The default Python buildpack allows you to do that: https://github.com/heroku/heroku-buildpack-python/blob/master/Readme.md IIRC you only need to include a runtime.txt with pypy-2.6.0 https://github.com/heroku/heroku-buildpack-python/blob/master/builds/runtimes/pypy-2.6.0 El jun 15, 2015 12:50 AM, "Ram Rachum" escribi?: > If I want to use a modern version of PyPy on Heroku (they currently only > allow PyPy 1.9 by default,) did someone make a Heroku buildpack with a > recent PyPy? That'll make it easy for many people to start using PyPy for > their web apps. > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ram at rachum.com Mon Jun 15 21:18:01 2015 From: ram at rachum.com (Ram Rachum) Date: Mon, 15 Jun 2015 22:18:01 +0300 Subject: [pypy-dev] Heroku PyPy buildpack In-Reply-To: References: Message-ID: 1. Great, thank you. . 2. If I was a person who was motivated to make PyPy used by more people... I would draw a very big distinction between "Modern Pypy probably works on Heroku" and "the docs clearly say that modern PyPy works on Heroku without having to ask." On Mon, Jun 15, 2015 at 9:59 PM, Samuel Villamonte wrote: > The default Python buildpack allows you to do that: > > https://github.com/heroku/heroku-buildpack-python/blob/master/Readme.md > > IIRC you only need to include a runtime.txt with > > pypy-2.6.0 > > > https://github.com/heroku/heroku-buildpack-python/blob/master/builds/runtimes/pypy-2.6.0 > El jun 15, 2015 12:50 AM, "Ram Rachum" escribi?: > >> If I want to use a modern version of PyPy on Heroku (they currently only >> allow PyPy 1.9 by default,) did someone make a Heroku buildpack with a >> recent PyPy? That'll make it easy for many people to start using PyPy for >> their web apps. >> >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From yury at shurup.com Mon Jun 15 21:49:11 2015 From: yury at shurup.com (Yury V. Zaytsev) Date: Mon, 15 Jun 2015 21:49:11 +0200 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: References: <1434186858.2899.395.camel@newpride> Message-ID: <1434397751.14419.215.camel@newpride> On Mon, 2015-06-15 at 08:46 +0200, Armin Rigo wrote: > > If someone could check if that's the case, please open an issue then > (http://bugs.pypy.org/). I don't think that's the case: $ openssl version -a OpenSSL 1.0.1e-fips 11 Feb 2013 built on: Thu Jun 4 19:38:28 UTC 2015 platform: linux-x86_64 options: bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int) blowfish(idx) compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -DTERMIO -Wall -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -Wa,--noexecstack -DPURIFY -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM OPENSSLDIR: "/etc/pki/tls" engines: dynamic Also, if you look into the -devel package: http://mirror.centos.org/centos/6/updates/x86_64/Packages/openssl-devel-1.0.1e-30.el6_6.7.x86_64.rpm You'll find in ec.h included from ecdh.h: typedef struct ec_key_st EC_KEY; and OPENSSL_NO_ECDH is not set in opensslconf-x86_64.h ... -- Sincerely yours, Yury V. Zaytsev From cherian.rosh at gmail.com Tue Jun 16 03:55:25 2015 From: cherian.rosh at gmail.com (Roshan Cherian) Date: Mon, 15 Jun 2015 18:55:25 -0700 Subject: [pypy-dev] pypy 2.6.0 failing with compile errors In-Reply-To: <1434397751.14419.215.camel@newpride> References: <1434186858.2899.395.camel@newpride> <1434397751.14419.215.camel@newpride> Message-ID: Thanks Armin and Yury. This was indeed a problem with the version on openssl. I have updated the openssl version and now its building fine without any changes in the include headers of openssl. Thanks, -Roshan On Mon, Jun 15, 2015 at 12:49 PM, Yury V. Zaytsev wrote: > On Mon, 2015-06-15 at 08:46 +0200, Armin Rigo wrote: > > > > If someone could check if that's the case, please open an issue then > > (http://bugs.pypy.org/). > > I don't think that's the case: > > $ openssl version -a > OpenSSL 1.0.1e-fips 11 Feb 2013 > built on: Thu Jun 4 19:38:28 UTC 2015 > platform: linux-x86_64 > options: bn(64,64) md2(int) rc4(16x,int) des(idx,cisc,16,int) idea(int) > blowfish(idx) > compiler: gcc -fPIC -DOPENSSL_PIC -DZLIB -DOPENSSL_THREADS -D_REENTRANT > -DDSO_DLFCN -DHAVE_DLFCN_H -DKRB5_MIT -m64 -DL_ENDIAN -DTERMIO -Wall -O2 > -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector > --param=ssp-buffer-size=4 -m64 -mtune=generic -Wa,--noexecstack -DPURIFY > -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 > -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM > -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM > OPENSSLDIR: "/etc/pki/tls" > engines: dynamic > > Also, if you look into the -devel package: > > > http://mirror.centos.org/centos/6/updates/x86_64/Packages/openssl-devel-1.0.1e-30.el6_6.7.x86_64.rpm > > You'll find in ec.h included from ecdh.h: > > typedef struct ec_key_st EC_KEY; > > and OPENSSL_NO_ECDH is not set in opensslconf-x86_64.h ... > > -- > Sincerely yours, > Yury V. Zaytsev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Tue Jun 16 08:47:13 2015 From: arigo at tunes.org (Armin Rigo) Date: Tue, 16 Jun 2015 08:47:13 +0200 Subject: [pypy-dev] Heroku PyPy buildpack In-Reply-To: References: Message-ID: Hi Ram, On 15 June 2015 at 21:18, Ram Rachum wrote: > 2. If I was a person who was motivated to make PyPy used by more people... I > would draw a very big distinction between "Modern Pypy probably works on > Heroku" and "the docs clearly say that modern PyPy works on Heroku without > having to ask." Is that somewhere in the PyPy docs? Google cannot find the sentence "Modern PyPy probably works on Heroku", so that must not be literal. Armin From ram at rachum.com Tue Jun 16 08:52:59 2015 From: ram at rachum.com (Ram Rachum) Date: Tue, 16 Jun 2015 09:52:59 +0300 Subject: [pypy-dev] Heroku PyPy buildpack In-Reply-To: References: Message-ID: No, I meant the Heroku docs: https://devcenter.heroku.com/articles/python-runtimes#available-runtimes I understand you don't control Heroku but if someone were to ensure that PyPy 2.6 works reliably there, without having to tweak anything, and bug Heroku about it, maybe they'll put it on the list and more people would use PyPy 2.6 on Heroku. Note that the list of Python versions in the link above isn't even the Heroku-endorsed list. They say only 2.7 and 3.4 are endorsed, so it's implied that the others are usable but not endorsed. Therefore I'm assuming it'll be easy to get them to update it from PyPy 1.9 to PyPy 2.6. On Tue, Jun 16, 2015 at 9:47 AM, Armin Rigo wrote: > Hi Ram, > > On 15 June 2015 at 21:18, Ram Rachum wrote: > > 2. If I was a person who was motivated to make PyPy used by more > people... I > > would draw a very big distinction between "Modern Pypy probably works on > > Heroku" and "the docs clearly say that modern PyPy works on Heroku > without > > having to ask." > > Is that somewhere in the PyPy docs? Google cannot find the sentence > "Modern PyPy probably works on Heroku", so that must not be literal. > > > Armin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Tue Jun 16 09:00:29 2015 From: arigo at tunes.org (Armin Rigo) Date: Tue, 16 Jun 2015 09:00:29 +0200 Subject: [pypy-dev] Heroku PyPy buildpack In-Reply-To: References: Message-ID: Hi Ram, On 16 June 2015 at 08:52, Ram Rachum wrote: > I understand you don't control Heroku but if someone were to ensure that > PyPy 2.6 works reliably there, without having to tweak anything, and bug > Heroku about it, maybe they'll put it on the list and more people would use > PyPy 2.6 on Heroku. In this discussion you're the one using Heroku, so you could be the "someone" of your sentence :-) Armin From ram at rachum.com Tue Jun 16 09:13:47 2015 From: ram at rachum.com (Ram Rachum) Date: Tue, 16 Jun 2015 10:13:47 +0300 Subject: [pypy-dev] Heroku PyPy buildpack In-Reply-To: References: Message-ID: Yes, I know :) I realize I'm suggesting other people, who work as volunteers, do work that I think should be done instead of doing it myself, and I'll understand if people wouldn't want to spend their personal time doing that. (Just like in my open-source projects people often make suggestions on features they want me to implement and I tell them I don't want to spend the time doing that.) What I would say though is that on the open-source projects that I maintain (much smaller than PyPy) I've done all the dirty work for them (dirty work == things that are important but that no one wants to do, like packaging) because I know no one else will, and because I know it'll be much much easier for me than other people because I know the project in and out and can solve technical problems much faster. So I'm pretty frustrated with the fact that PyPy could be much easier for people to use, and it seems like the focus of the project is to make PyPy faster and faster instead of making it easier to use. Whether PyPy is x7 faster or x8 faster is less important in my opinion than whether it's easy to start using, so if the goal is to get PyPy to be more popular (hopefully on CPython levels) I think that ease-of-use is the biggest priority. Making PyPy easy to install on Heroku is one thing. Providing an installer for Windows is another. I've also heard dozens of times that it's possible to use third-party packages written in C on PyPy (like psycopg2 or wxpython) but it's not clear how. Do I have to compile them or build them or any other kind of technical work? For me personally it's a barrier, things always go wrong for me when I try to build a program so I'd much rather download a binary (with an installer when applicable.) So that's another barrier that can be removed. Basically have a conversation with an average Python user, "Are you using PyPy? Why not? How can I fix that?" But again, these are just suggestions, given with the hopes that they'll help. No one is obligated to agree with them or follow them. Thanks, Ram. On Tue, Jun 16, 2015 at 10:00 AM, Armin Rigo wrote: > Hi Ram, > > On 16 June 2015 at 08:52, Ram Rachum wrote: > > I understand you don't control Heroku but if someone were to ensure that > > PyPy 2.6 works reliably there, without having to tweak anything, and bug > > Heroku about it, maybe they'll put it on the list and more people would > use > > PyPy 2.6 on Heroku. > > In this discussion you're the one using Heroku, so you could be the > "someone" of your sentence :-) > > > Armin > -------------- next part -------------- An HTML attachment was scrubbed... URL: From samo at meluria.com Tue Jun 16 15:02:08 2015 From: samo at meluria.com (Samuel Villamonte) Date: Tue, 16 Jun 2015 08:02:08 -0500 Subject: [pypy-dev] Heroku PyPy buildpack In-Reply-To: References: Message-ID: > I understand you don't control Heroku but if someone were to ensure that PyPy 2.6 works reliably there. There are already several people in the Heroku GitHub page that the moment there's a new PyPy release, they create a pull request, see for yourself: https://github.com/heroku/heroku-buildpack-python/issues?utf8=%E2%9C%93&q=pypy Heroku is by no means easy to install and use (at least in Ubuntu) just because there is a tutorial, you need to be proficient in the command line, yet people use it because it lets you try new stuff. Have you tried a new dyno with a pypy runtime? Did it work out of the box? Was it easy to setup? Maybe you could create an issue in their issue tracker and ask to update their tutorial. Then you could move to ask the same of other providers, e.g. Digital Ocean, Amazon Web Services, Google App Engine, etc. And honestly I think you just answered yourself here: > Just like in my open-source projects people often make suggestions on > features they want me to implement and I tell them I don't want to spend > the time doing that. > When I lurk in the IRC channel I can almost imagine the core devs telling jokes in assembler, and my plans to conquer the world are currently on hold due to my daytime job, should I complain about that too? An open source project is what you make of it, pull requests and/or bugs are welcome here, if you think they're not, just subscribe to the cffi issue tracker for starters, I think Armin is ensuring it's Turing complete before the end of year or something. -------------- next part -------------- An HTML attachment was scrubbed... URL: From migrau at uji.es Wed Jun 17 02:47:00 2015 From: migrau at uji.es (Miguel Grau) Date: Wed, 17 Jun 2015 09:47:00 +0900 Subject: [pypy-dev] Scipy Message-ID: <5580C384.2080006@uji.es> Dear pypy users, Is pypy working with scipy? I need numpy&scipy for pypy. I installed correctly the nightly PyPy and the NumPy fork but when I try to install scipy I get this error: /usr/include/numpy/npy_math.h:452:27: error: unknown type name ?npy_clongdouble? npy_clongdouble npy_csinl(npy_clongdouble z); ^ error: Command "cc -O2 -fPIC -Wimplicit -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/site-packages/scipy/scipy/special -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/include -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/include -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/site-packages/scipy/scipy/special/c_misc -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/include -c scipy/special/c_misc/struve.c -o build/temp.linux-x86_64-2.7/scipy/special/c_misc/struve.o" failed with exit status 1 Any idea? Thank you! Miguel From matti.picus at gmail.com Wed Jun 17 16:40:04 2015 From: matti.picus at gmail.com (Matti Picus) Date: Wed, 17 Jun 2015 17:40:04 +0300 Subject: [pypy-dev] Scipy In-Reply-To: <5580C384.2080006@uji.es> References: <5580C384.2080006@uji.es> Message-ID: <558186C4.9010600@gmail.com> Hi Miguel. I would be very suprised if scipy worked with our as-yet-incomplete numpy implementation and fork. This particular error is caused by a missing pypy-compatible npy_math.h header file. It may help to take a look at where we (mis)placed the definitions from that header (you should find our headers in /home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/include/numpy ) and try to create a pypy-compatible version, but you may quickly run into other errors and incomatibilities. Matti On 17/06/15 03:47, Miguel Grau wrote: > Dear pypy users, > > Is pypy working with scipy? I need numpy&scipy for pypy. I installed > correctly the nightly PyPy and the NumPy fork but when I try to > install scipy I get this error: > > /usr/include/numpy/npy_math.h:452:27: error: unknown type name > ?npy_clongdouble? > npy_clongdouble npy_csinl(npy_clongdouble z); > ^ > error: Command "cc -O2 -fPIC -Wimplicit > -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/site-packages/scipy/scipy/special > -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/include > -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/include > -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/site-packages/scipy/scipy/special/c_misc > -I/home/user/apps/pypy-c-jit-78122-2c4887192c62-linux64/include -c > scipy/special/c_misc/struve.c -o > build/temp.linux-x86_64-2.7/scipy/special/c_misc/struve.o" failed with > exit status 1 > > Any idea? Thank you! > > Miguel > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev From techtonik at gmail.com Fri Jun 19 16:52:48 2015 From: techtonik at gmail.com (anatoly techtonik) Date: Fri, 19 Jun 2015 17:52:48 +0300 Subject: [pypy-dev] .whl depending on CFFI Message-ID: Hi, Should binary wheels depend on CFFI? For some reason this seems wrong to me (the package ships with compiled binary modules): >pip install tdl Collecting tdl Downloading tdl-1.3.0-cp27-none-win32.whl (1.6MB) 100% |################################| 1.6MB 50kB/s Collecting cffi>=1.0.0 (from tdl) Downloading cffi-1.1.2-cp27-none-win32.whl (121kB) 100% |################################| 122kB 362kB/s Collecting pycparser (from cffi>=1.0.0->tdl) Downloading pycparser-2.14.tar.gz (223kB) 100% |################################| 225kB 248kB/s Installing collected packages: pycparser, cffi, tdl Running setup.py install for pycparser Build the lexing/parsing tables Successfully installed cffi-1.1.2 pycparser-2.14 tdl-1.3.0 -- anatoly t. From techtonik at gmail.com Fri Jun 19 17:12:00 2015 From: techtonik at gmail.com (anatoly techtonik) Date: Fri, 19 Jun 2015 18:12:00 +0300 Subject: [pypy-dev] rogue CFFI speedups #....@k....$...# Message-ID: Hi, Just wanted to let you know of awesome 3x speedup after python-tdl was ported to CFFI. python-tdl is a libtcod binding for Python. The wrapped libtcod is the very rad ?Doryen Library" used to build roguelikes in C world. I am sure that having it in Python will pave a road to more pleasant text mode interfaces. =) There were some issues during the porting and packaging process. I think you might be interested to check them out: https://github.com/HexDecimal/python-tdl/issues/5 -- anatoly t. From arigo at tunes.org Fri Jun 19 18:20:03 2015 From: arigo at tunes.org (Armin Rigo) Date: Fri, 19 Jun 2015 18:20:03 +0200 Subject: [pypy-dev] .whl depending on CFFI In-Reply-To: References: Message-ID: Hi Anatoly, I can't help you much with wheels, but try the CFFI mailing list instead of PyPy's: python-cffi at googlegroups.com Armin From glenn.chin at radware.com Sat Jun 20 20:42:45 2015 From: glenn.chin at radware.com (Glenn Chin) Date: Sat, 20 Jun 2015 18:42:45 +0000 Subject: [pypy-dev] "ImportError: No module named httplib2" Message-ID: On my Ubuntu machine, there's an httplib2 directory under /usr/lib/python2.7/dist-packages . httplib2 imports and works fine in a Python script. However, the above error message appears when I try to run the same script using PyPy 2.6 . I suspect it's a configuration problem. Any suggestions? Glenn -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Sat Jun 20 22:43:19 2015 From: arigo at tunes.org (Armin Rigo) Date: Sat, 20 Jun 2015 22:43:19 +0200 Subject: [pypy-dev] "ImportError: No module named httplib2" In-Reply-To: References: Message-ID: Hi Glenn, On 20 June 2015 at 20:42, Glenn Chin wrote: > /usr/lib/python2.7/dist-packages . > > httplib2 imports and works fine in a Python script. However, the above > error message appears when I try to run the same script using PyPy 2.6 . I > suspect it?s a configuration problem. Any suggestions? This looks like this FAQ would help you: pypy.readthedocs.org/en/latest/faq.html#module-xyz-does-not-work-with-pypy-importerror . Please follow the answer first. Does it help? If not, feel free to ask again here (or on irc, #pypy at irc.freenode.net). A bient?t, Armin. From daetalusun at gmail.com Sun Jun 21 01:33:29 2015 From: daetalusun at gmail.com (Boxiang Sun) Date: Sun, 21 Jun 2015 07:33:29 +0800 Subject: [pypy-dev] Questions about build new extension with RPython Message-ID: Hi all, I am a newbie in PyPy. But with some experience in CPython, and also OpenCV-Python binding and OpenCV-Julia binding.I want to bring OpenCV into PyPy. Then use PyPy to do my research. First, I read some PyPy and RPython document in recent days. I want to wrap OpenCV in PyPy in "low level". Like OpenCV-CPython, it use Python-C API and Numpy C-API to wrap function and class. Then write a autowrap script to wrap it. In this way, OpenCV-CPython can communicate with NumPy array type. If my understanding is correct. NumPy-PyPy wrote in RPython, wrap the corresponding C and Fortran function. I want wrap OpenCV in PyPy just like OpenCV-CPython. Let NumPy ndarray hold the image matrix. But RPython documentation said "It(Write with RPython) cannot be used by any 3rd-party module". Does it mean if wrap OpenCV in PyPy with cffi. OpenCV-PyPy could not use ndarray? I plan to use RPython, but RPython documentation said it need rebuild PyPy it self, and the module write in RPython will become a built-in module. Rebuild PyPy seems unacceptable in OpenCV-PyPy. Is there has a way to wrap OpenCV in PyPy that could communicate with NumPy-PyPy and without rebuild PyPy it self? Please correct me if my understanding was wrong. Regards, Sun -------------- next part -------------- An HTML attachment was scrubbed... URL: From lac at openend.se Sun Jun 21 11:52:03 2015 From: lac at openend.se (Laura Creighton) Date: Sun, 21 Jun 2015 11:52:03 +0200 Subject: [pypy-dev] Paper on the HOPE JIT for Python Message-ID: <201506210952.t5L9q3YL031549@fido.openend.se> http://www.sciencedirect.com/science/article/pii/S2213133714000687 I think some of our poor performance is because they never let the jit warm up, but should we grab some of their benchmarks and see if we can do better? Laura From fijall at gmail.com Sun Jun 21 12:30:33 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Sun, 21 Jun 2015 12:30:33 +0200 Subject: [pypy-dev] Questions about build new extension with RPython In-Reply-To: References: Message-ID: Hi Boxiang. You're far better off doing it with cffi and writing part of it in C (pure C) or Python. Cffi on pypy is quite well optimized and should not really present a performance overhead. On Sun, Jun 21, 2015 at 1:33 AM, Boxiang Sun wrote: > Hi all, > > I am a newbie in PyPy. But with some experience in CPython, and also > OpenCV-Python binding and OpenCV-Julia binding.I want to bring OpenCV into > PyPy. Then use PyPy to do my research. > > First, I read some PyPy and RPython document in recent days. I want to wrap > OpenCV in PyPy in "low level". Like OpenCV-CPython, it use Python-C API and > Numpy C-API to wrap function and class. Then write a autowrap script to wrap > it. In this way, OpenCV-CPython can communicate with NumPy array type. > > If my understanding is correct. NumPy-PyPy wrote in RPython, wrap the > corresponding C and Fortran function. > > I want wrap OpenCV in PyPy just like OpenCV-CPython. Let NumPy ndarray hold > the image matrix. But RPython documentation said "It(Write with RPython) > cannot be used by any 3rd-party module". Does it mean if wrap OpenCV in PyPy > with cffi. OpenCV-PyPy could not use ndarray? > > I plan to use RPython, but RPython documentation said it need rebuild PyPy > it self, and the module write in RPython will become a built-in module. > Rebuild PyPy seems unacceptable in OpenCV-PyPy. > > Is there has a way to wrap OpenCV in PyPy that could communicate with > NumPy-PyPy and without rebuild PyPy it self? > > Please correct me if my understanding was wrong. > > Regards, > Sun > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > From arigo at tunes.org Sun Jun 21 12:33:06 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 21 Jun 2015 12:33:06 +0200 Subject: [pypy-dev] tkinter tests broken Message-ID: Hi Amaury, In fd331e4bf733 you did an untested change to the tkinter library; as it turns out, the CPython tests find problems: http://buildbot.pypy.org/summary/longrepr?testname=unmodified&builder=pypy-c-jit-linux-x86-32&build=2727&mod=lib-python.2.7.test.test_tcl Can you fix the situation? Thanks! Armin From arigo at tunes.org Sun Jun 21 13:04:57 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 21 Jun 2015 13:04:57 +0200 Subject: [pypy-dev] Questions about build new extension with RPython In-Reply-To: References: Message-ID: Hi Boxiang, On 21 June 2015 at 01:33, Boxiang Sun wrote: > Does it mean if wrap OpenCV in PyPy > with cffi. OpenCV-PyPy could not use ndarray? I don't know OpenCV myself, but writing a CFFI module accessing it should be easy, even if there are functions that take numpy arrays. You can do: ffi.from_buffer(some_ndarray) which returns a ffi ``char *`` pointer, pointing to the data from the ndarray. You can pass this raw pointer to C functions from OpenCV. There is no copy of the data; if the C function modifies the data, it will be modified in the numpy array too. A bient?t, Armin. From amauryfa at gmail.com Sun Jun 21 14:11:36 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Sun, 21 Jun 2015 14:11:36 +0200 Subject: [pypy-dev] tkinter tests broken In-Reply-To: References: Message-ID: Hi Armin, 2015-06-21 12:33 GMT+02:00 Armin Rigo : > Hi Amaury, > > In fd331e4bf733 you did an untested change to the tkinter library; as > it turns out, the CPython tests find problems: > > > http://buildbot.pypy.org/summary/longrepr?testname=unmodified&builder=pypy-c-jit-linux-x86-32&build=2727&mod=lib-python.2.7.test.test_tcl > > Can you fix the situation? Thanks! Actually my changes were trying to fix the test failures in this test_tcl file, since the merge of stdlib-2.7.10. This Tcl_NewWideIntObj function is used probably only in the 32bit case. Should be fixed with 6453697f3a30. -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From yury at shurup.com Sun Jun 21 14:25:33 2015 From: yury at shurup.com (Yury V. Zaytsev) Date: Sun, 21 Jun 2015 14:25:33 +0200 Subject: [pypy-dev] Paper on the HOPE JIT for Python In-Reply-To: <201506210952.t5L9q3YL031549@fido.openend.se> References: <201506210952.t5L9q3YL031549@fido.openend.se> Message-ID: <1434889533.2581.67.camel@newpride> On Sun, 2015-06-21 at 11:52 +0200, Laura Creighton wrote: > > > http://www.sciencedirect.com/science/article/pii/S2213133714000687 I'm curious whether I'm the only one to find this paper disappointing? To summarize, the authors developed a translation system into C++ for a very restricted subset of Python, as well as some machinery to automagically compile and make translated functions available to the Python land. How justified is it to call this a method-level JIT, I find rather questionable; following this line of thinking, even Cython suddenly also becomes a JIT (see pyximport). Anyways, the claimed advantage of this exercise is that they are able to deduce the types, and so idiomatic Python code doesn't need to be supplemented with type annotations. However, if one looks at the benchmark codes, HOPE-friendly functions do not look much like idiomatic Python code, so this argument is quite far fetched. Amusingly, the benchmarks show that Cython beats HOPE in most cases, and when it doesn't, it's either a very questionable case (such as the "simplify" benchmark, don't get me started here...), or strange and probably suboptimal Cython implementation ("star" benchmark, where older NumPy mode instead of memory views is used, np.sqrt() is called in a supposedly tight loop, unclear whether the call to np.sum() is actually faster than unrolling, etc.). In as far as PyPy is concerned, it so appears that the time it takes to run most of their benchmarks about 100 times (as they claim they did) is generally << 1 second, and most loops were like 1000 iterations anyways, so most likely JIT didn't kick in any case (if I remember correctly, the heuristic was some odd number of iterations that is slightly higher than 1000). I couldn't find what exactly they ran on PyPy and how they did it from a cursory look, so it's unclear. In conclusion, I'm afraid there is not much at all to learn from this publication... ... except that, maybe, this kind of papers should be reviewed by experts on the subject, and not by domain scientists (in this case, astrophysicists), who are generally unlikely to reject such works, as long as it looks reasonably "scientific" and the grammar is good enough. -- Sincerely yours, Yury V. Zaytsev From arigo at tunes.org Sun Jun 21 14:50:35 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 21 Jun 2015 14:50:35 +0200 Subject: [pypy-dev] Paper on the HOPE JIT for Python In-Reply-To: <1434889533.2581.67.camel@newpride> References: <201506210952.t5L9q3YL031549@fido.openend.se> <1434889533.2581.67.camel@newpride> Message-ID: Hi Yury, On 21 June 2015 at 14:25, Yury V. Zaytsev wrote: > In conclusion, I'm afraid there is not much at all to learn from this > publication... > > ... except that, maybe, this kind of papers should be reviewed by > experts on the subject, and not by domain scientists (in this case, > astrophysicists), who are generally unlikely to reject such works, as > long as it looks reasonably "scientific" and the grammar is good enough. Thanks for making and sharing your observations. There is not much we can actively do. Of course running a loop only 100 times gives a bad idea about the performance of any real JIT. (Did they include the time spent calling gcc/llvm, for some of the other "JITs"?) We can however point people to your mail, if they come and complain to us. It gives a nice summary of a point of view much closer to our own. That said, I'm afraid the scientific community will continue to produce "JITs" as long as there is no well-accepted alternative to CPython. I think that fighting every attempt or paper we disagree with is pointless. I'd rather get PyPy to progress to a point where it be can used as a drop-in replacement of CPython in this domain too. (I'm not in numpy at all myself, so it's more a would-be-nice wish here.) A bient?t, Armin. From daetalusun at gmail.com Sun Jun 21 19:41:04 2015 From: daetalusun at gmail.com (Boxiang Sun) Date: Mon, 22 Jun 2015 01:41:04 +0800 Subject: [pypy-dev] Questions about build new extension with RPython In-Reply-To: References: Message-ID: Thanks to Armin and Maciej. I will try to build a OpenCV-PyPy prototype with cffi first. Regards, Sun 2015-06-21 19:04 GMT+08:00 Armin Rigo : > Hi Boxiang, > > On 21 June 2015 at 01:33, Boxiang Sun wrote: > > Does it mean if wrap OpenCV in PyPy > > with cffi. OpenCV-PyPy could not use ndarray? > > I don't know OpenCV myself, but writing a CFFI module accessing it > should be easy, even if there are functions that take numpy arrays. > You can do: > > ffi.from_buffer(some_ndarray) > > which returns a ffi ``char *`` pointer, pointing to the data from the > ndarray. You can pass this raw pointer to C functions from OpenCV. > There is no copy of the data; if the C function modifies the data, it > will be modified in the numpy array too. > > > A bient?t, > > Armin. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From yury at shurup.com Sun Jun 21 21:37:20 2015 From: yury at shurup.com (Yury V. Zaytsev) Date: Sun, 21 Jun 2015 21:37:20 +0200 Subject: [pypy-dev] Paper on the HOPE JIT for Python In-Reply-To: References: <201506210952.t5L9q3YL031549@fido.openend.se> <1434889533.2581.67.camel@newpride> Message-ID: <1434915440.2581.326.camel@newpride> Hi Armin, On Sun, 2015-06-21 at 14:50 +0200, Armin Rigo wrote: > > There is not much we can actively do. Of course running a loop only > 100 times gives a bad idea about the performance of any real JIT. Just to clarify, from what I understood, they basically ran timeit.repeat(stmt, repeat=100, number=1) [1] where `stmt` is each of their benchmarks. [1]: https://github.com/cosmo-ethz/hope/blob/master/benchmarks/native_cpp_gen.ipynb The benchmarks themselves are partly taken from the Julia website (fib, quicksort, pisum), and partly original (polynomial, simplify, pairwise distance and point spread function). Some benchmarks contain nested inner loops (e.g. pisum has an outer loop that runs 500 times and an inner loop that runs 10000 times), and some do not (e.g. fib measures function call overhead, yay!). Unlike for the rest of the tools, the raw data for PyPy is not available, so it's unclear to me whether they allowed the JIT to warm up in all cases, which is what I alluded to in my previous email. By the way, upon closer inspection, it seems that they have actually tried some of the optimizations that I've mentioned for the Cython implementation of the "point spread function", and it ran faster than their reference implementation in C++, which is why, I guess, they chose to not to include it in the table ;-), and used the unoptimized version instead... > (Did they include the time spent calling gcc/llvm, for some of the > other "JITs"?) No, they didn't, but what they did was to call each function once with the right parameters at the beginning of the benchmarking session in order to allow all of the tools to compile the code (and infer types, when applicable). > We can however point people to your mail, if they come and complain to > us. It gives a nice summary of a point of view much closer to our own. I wonder if I should let the authors know of this thread; on one hand, they might learn something from it, but, on the other hand, detailed discussion of the flaws of this paper is probably offtopic for this list. On the third hand ^__^, however, I would be uncomfortable with offlist discussions, as they surely will take a lot of my private time, but likely have very little yield for the world :-/ > That said, I'm afraid the scientific community will continue to > produce "JITs" as long as there is no well-accepted alternative to > CPython. I think that fighting every attempt or paper we disagree with > is pointless. I'd rather get PyPy to progress to a point where it be > can used as a drop-in replacement of CPython in this domain too. (I'm > not in numpy at all myself, so it's more a would-be-nice wish here.) Yes, I agree with you on that, but personally, I don't see much of a problem with folks out there playing with source to source translation and type inference; to my mind that's perfectly alright. My grief with the re-inventors of "JITs" is that as a rule they use confusing terminology, conduct flawed benchmarks and publish their reports in specialist journals, which are not able to properly screen such articles... oh well. -- Sincerely yours, Yury V. Zaytsev From arigo at tunes.org Sun Jun 21 22:42:35 2015 From: arigo at tunes.org (Armin Rigo) Date: Sun, 21 Jun 2015 22:42:35 +0200 Subject: [pypy-dev] Paper on the HOPE JIT for Python In-Reply-To: <1434915440.2581.326.camel@newpride> References: <201506210952.t5L9q3YL031549@fido.openend.se> <1434889533.2581.67.camel@newpride> <1434915440.2581.326.camel@newpride> Message-ID: Hi Yury, On 21 June 2015 at 21:37, Yury V. Zaytsev wrote: > Yes, I agree with you on that, but personally, I don't see much of a > problem with folks out there playing with source to source translation > and type inference; to my mind that's perfectly alright. Yes, sorry if I was unclear. It's also ok for me. That's what I alluded to: I don't see any reason to fight against the "non-PyPy" approaches---not that I consider them as uninteresting nonsense, but simply that they are very different approaches, and cross-discussions don't seem to work at this point (it seems that some of us tried and failed to get some discussions started with numpy people; please be aware that this is second-hand experience though.) Until we have good enough results to not be so easily ignorable, I guess the situation won't change. (Alternatively, we need a champion from the community ready to write papers for the same kinds of journals... which, I agree with you, is a strange place to write about JIT compilers) A bient?t, Armin. From lockhart at csl.cornell.edu Mon Jun 22 17:17:24 2015 From: lockhart at csl.cornell.edu (Derek Lockhart) Date: Mon, 22 Jun 2015 11:17:24 -0400 Subject: [pypy-dev] RFFI Usage and Documentation Message-ID: After a bit of a struggle I finally got RFFI working for a shared libary I had compiled. I found a few strange discrepancies in the behavior of ExternalCompilitionInfo on OSX I thought may benefit from fixes to make behavior more consistent. === RPython Translation vs. Python Execution Strangeness === Given a shared library I had compiled named libsoftfloat.so: - ExternalCompilationInfo( libraries = ['libsoftfloat'] ) and libname == libsoftfloat.so - python execution: Error: "cannot find library libsoftfloat" - rpython translation: Error: "ld: library not found for -llibsoftfloat" - ExternalCompilationInfo( libraries = ['softfloat'] ) and libname == libsoftfloat.so - python execution: Error: "cannot find library softfloat" - rpython translation: Works! The problem with RFFI during Python execution appears to be that on OSX it checks for the library suffix of .dylib, **not** .so: - ExternalCompilationInfo( libraries = ['libsoftfloat'] ) and libname == libsoftfloat.dylib - python execution: Works! - rpython translation: Error: "ld: library not found for -llibsoftfloat" - ExternalCompilationInfo( libraries = ['softfloat'] ) and libname == libsoftfloat.dylib - python execution: Works! - rpython translation: Works! Some naming schemes work on just python execution, some on just rpython translation. It would be nice if these failed/worked consistently in both modes. In particular, I think on OSX the library lookup for RFFI should look for both .so and .dylib, not just .dylib since it seems to be fairly common practice to generate .so files? Also, the libraries naming convention passed to ExternalCompilationInfo is a bit inconsistent/foreign for someone coming from CFFI and using ffi.dlopen(). === Documentation === I really couldn't figure out how to use RFFI from the RPython docs or from the PyPy source. I started off using these resources: - https://rpython.readthedocs.org/en/latest/rffi.html - https://bitbucket.org/pypy/pypy/src/tip/rpython/rlib/_rsocket_rffi.py - https://bitbucket.org/pypy/pypy/src/tip/pypy/module/crypt/interp_crypt.py The only way I really figured out how to use it was from this patch submitted by the libgccjit guy that had some simple examples on how to use RFFI: - https://mail.python.org/pipermail/pypy-dev/2014-December/012947.html What would be really nice is some example of how to write a simple function in C, compile it into a shared library, and use it via RFFI. Even better, an example mapping a CFFI use case to the RFFI interface. I personally learn how to use APIs much more easily with concrete examples; for example, I created a little git repo as a self-demonstration of how to use the new CFFI APIs with a non-trivial library: - https://github.com/dmlockhart/python-softfloat-cffi/ I'd be willing to help a bit with the docs, if it's agreed updates would be appreciated. Derek -------------- next part -------------- An HTML attachment was scrubbed... URL: From lockhart at csl.cornell.edu Mon Jun 22 18:17:31 2015 From: lockhart at csl.cornell.edu (Derek Lockhart) Date: Mon, 22 Jun 2015 12:17:31 -0400 Subject: [pypy-dev] RFFI Usage and Documentation In-Reply-To: References: Message-ID: To further expand on the strangeness, when using my libsoftfloat.dylib file and trying to create getters/setters to an internal variable using rffi.CExternVariable, I get the following error: File "/Users/dmlockhart/vc/hg-opensource/pypy/rpython/rtyper/lltypesystem/ll2ctypes.py", line 1169, in get_ctypes_callable clib = dllclass._dlltype(libpath, **load_library_kwargs) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ctypes/__init__.py", line 365, in __init__ self._handle = _dlopen(self._name, mode) OSError: dlopen(/var/folders/y4/c0cyz0bx6bjg5lzyd5prllbh0000gn/T/usession-default-109/shared_cache/externmod.dylib, 6): Library not loaded: libsoftfloat.so Referenced from: /var/folders/y4/c0cyz0bx6bjg5lzyd5prllbh0000gn/T/usession-default-109/shared_cache/externmod.dylib Reason: image not found So using rffi.llexternal expects a .dylib file on OSX, but rffi.CExternVariable expects a .so file. Creating a copy of the .dylib file so I have **both** a .so and .dylib file makes this error go away; but I suspect internal state of the library would not be consistent with two copies... On Mon, Jun 22, 2015 at 11:17 AM, Derek Lockhart wrote: > After a bit of a struggle I finally got RFFI working for a shared libary I > had compiled. I found a few strange discrepancies in the behavior of > ExternalCompilitionInfo on OSX I thought may benefit from fixes to make > behavior more consistent. > > === RPython Translation vs. Python Execution Strangeness === > > Given a shared library I had compiled named libsoftfloat.so: > > - ExternalCompilationInfo( libraries = ['libsoftfloat'] ) and libname == > libsoftfloat.so > - python execution: Error: "cannot find library libsoftfloat" > - rpython translation: Error: "ld: library not found for -llibsoftfloat" > > - ExternalCompilationInfo( libraries = ['softfloat'] ) and libname == > libsoftfloat.so > - python execution: Error: "cannot find library softfloat" > - rpython translation: Works! > > The problem with RFFI during Python execution appears to be that on OSX it > checks for the library suffix of .dylib, **not** .so: > > - ExternalCompilationInfo( libraries = ['libsoftfloat'] ) and libname == > libsoftfloat.dylib > - python execution: Works! > - rpython translation: Error: "ld: library not found for -llibsoftfloat" > > - ExternalCompilationInfo( libraries = ['softfloat'] ) and libname == > libsoftfloat.dylib > - python execution: Works! > - rpython translation: Works! > > Some naming schemes work on just python execution, some on just rpython > translation. It would be nice if these failed/worked consistently in both > modes. In particular, I think on OSX the library lookup for RFFI should > look for both .so and .dylib, not just .dylib since it seems to be fairly > common practice to generate .so files? > > Also, the libraries naming convention passed to ExternalCompilationInfo is > a bit inconsistent/foreign for someone coming from CFFI and using > ffi.dlopen(). > > === Documentation === > > I really couldn't figure out how to use RFFI from the RPython docs or from > the PyPy source. I started off using these resources: > > - https://rpython.readthedocs.org/en/latest/rffi.html > - https://bitbucket.org/pypy/pypy/src/tip/rpython/rlib/_rsocket_rffi.py > - > https://bitbucket.org/pypy/pypy/src/tip/pypy/module/crypt/interp_crypt.py > > The only way I really figured out how to use it was from this patch > submitted by the libgccjit guy that had some simple examples on how to use > RFFI: > > - https://mail.python.org/pipermail/pypy-dev/2014-December/012947.html > > What would be really nice is some example of how to write a simple > function in C, compile it into a shared library, and use it via RFFI. Even > better, an example mapping a CFFI use case to the RFFI interface. I > personally learn how to use APIs much more easily with concrete examples; > for example, I created a little git repo as a self-demonstration of how to > use the new CFFI APIs with a non-trivial library: > > - https://github.com/dmlockhart/python-softfloat-cffi/ > > I'd be willing to help a bit with the docs, if it's agreed updates would > be appreciated. > > Derek > -------------- next part -------------- An HTML attachment was scrubbed... URL: From rymg19 at gmail.com Mon Jun 22 18:30:25 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Mon, 22 Jun 2015 11:30:25 -0500 Subject: [pypy-dev] RFFI Usage and Documentation In-Reply-To: References: Message-ID: <8001ED48-6304-45DA-95A4-5268BB454412@gmail.com> On June 22, 2015 10:17:24 AM CDT, Derek Lockhart wrote: >After a bit of a struggle I finally got RFFI working for a shared >libary I >had compiled. I found a few strange discrepancies in the behavior of >ExternalCompilitionInfo on OSX I thought may benefit from fixes to make >behavior more consistent. > >=== RPython Translation vs. Python Execution Strangeness === > >Given a shared library I had compiled named libsoftfloat.so: > >- ExternalCompilationInfo( libraries = ['libsoftfloat'] ) and libname >== >libsoftfloat.so > - python execution: Error: "cannot find library libsoftfloat" >- rpython translation: Error: "ld: library not found for >-llibsoftfloat" > >- ExternalCompilationInfo( libraries = ['softfloat'] ) and libname == >libsoftfloat.so > - python execution: Error: "cannot find library softfloat" > - rpython translation: Works! > >The problem with RFFI during Python execution appears to be that on OSX >it >checks for the library suffix of .dylib, **not** .so: > >- ExternalCompilationInfo( libraries = ['libsoftfloat'] ) and libname >== >libsoftfloat.dylib > - python execution: Works! >- rpython translation: Error: "ld: library not found for >-llibsoftfloat" > >- ExternalCompilationInfo( libraries = ['softfloat'] ) and libname == >libsoftfloat.dylib > - python execution: Works! > - rpython translation: Works! > >Some naming schemes work on just python execution, some on just rpython >translation. It would be nice if these failed/worked consistently in >both >modes. In particular, I think on OSX the library lookup for RFFI >should >look for both .so and .dylib, not just .dylib since it seems to be >fairly >common practice to generate .so files? > >Also, the libraries naming convention passed to ExternalCompilationInfo >is >a bit inconsistent/foreign for someone coming from CFFI and using >ffi.dlopen(). > >=== Documentation === > >I really couldn't figure out how to use RFFI from the RPython docs or >from >the PyPy source. I started off using these resources: > >- https://rpython.readthedocs.org/en/latest/rffi.html >- https://bitbucket.org/pypy/pypy/src/tip/rpython/rlib/_rsocket_rffi.py >- >https://bitbucket.org/pypy/pypy/src/tip/pypy/module/crypt/interp_crypt.py I've been meaning to write a RFFI blog post for a bit now. IMO, the best learning resource is rlib: do a grep for 'rffi' in rpython/rlib and look at the referenced files. Another handy example was a PortAudio wrapper for RPython (I believe it was called rpyportaudio?). > >The only way I really figured out how to use it was from this patch >submitted by the libgccjit guy that had some simple examples on how to >use >RFFI: > >- https://mail.python.org/pipermail/pypy-dev/2014-December/012947.html > >What would be really nice is some example of how to write a simple >function >in C, compile it into a shared library, and use it via RFFI. Even >better, >an example mapping a CFFI use case to the RFFI interface. I personally >learn how to use APIs much more easily with concrete examples; for >example, >I created a little git repo as a self-demonstration of how to use the >new >CFFI APIs with a non-trivial library: > >- https://github.com/dmlockhart/python-softfloat-cffi/ > >I'd be willing to help a bit with the docs, if it's agreed updates >would be >appreciated. > >Derek > > >------------------------------------------------------------------------ > >_______________________________________________ >pypy-dev mailing list >pypy-dev at python.org >https://mail.python.org/mailman/listinfo/pypy-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From arigo at tunes.org Mon Jun 22 18:46:08 2015 From: arigo at tunes.org (Armin Rigo) Date: Mon, 22 Jun 2015 18:46:08 +0200 Subject: [pypy-dev] RFFI Usage and Documentation In-Reply-To: References: Message-ID: Hi Derek, On 22 June 2015 at 17:17, Derek Lockhart wrote: > After a bit of a struggle I finally got RFFI working for a shared libary I > had compiled. I found a few strange discrepancies in the behavior of > ExternalCompilitionInfo on OSX I thought may benefit from fixes to make > behavior more consistent. Before translation, we use a horrible hack to access the library for tests, in rpython/rtyper/lltypesystem/ll2ctypes.py. The logic so far: libpath = None ext = platform.so_ext # <- this is where ".dylib" comes from on OS/X prefixes = platform.so_prefixes # <- on OS/X this is ('',) for dir in eci.library_dirs: if libpath: break for prefix in prefixes: tryfile = os.path.join(dir, prefix + libname + '.' + ext) if os.path.isfile(tryfile): libpath = tryfile break if not libpath: libpath = ctypes.util.find_library(libname) # <- magic from ctypes if not libpath: libpath = _findLib_gcc_fallback(libname) # <- magic from us if not libpath and os.path.isabs(libname): libpath = libname if libpath: This is meant to emulate what will occur after translation to C, but is obviously approximate. I'm guessing that 'libsoftfloat' is found here (but not after translation) because of ctypes.util.find_library(). And I'm guessing that the code above only looks for '.dylib' simply because that's platform.so_ext so far. I fear that I cannot blindly change this logic and expect it to work better. At this point it's up to you to try to tweak it for OS/X and propose a patch. > === Documentation === > (...) > What would be really nice is some example of how to write a simple function > in C, compile it into a shared library, and use it via RFFI. Even better, an > example mapping a CFFI use case to the RFFI interface. I suppose the very best would be for us to deprecate RFFI and replace it with CFFI... A bient?t, Armin. From arigo at tunes.org Tue Jun 23 09:48:47 2015 From: arigo at tunes.org (Armin Rigo) Date: Tue, 23 Jun 2015 09:48:47 +0200 Subject: [pypy-dev] tkinter tests broken In-Reply-To: References: Message-ID: Hi Amaury, On 21 June 2015 at 14:11, Amaury Forgeot d'Arc wrote: > 2015-06-21 12:33 GMT+02:00 Armin Rigo : >> Can you fix the situation? Thanks! > > Should be fixed with 6453697f3a30. Thanks for fixing half of the failures :-) However, the other half still remains: http://buildbot.pypy.org/summary/longrepr?testname=unmodified&builder=pypy-c-jit-linux-x86-32&build=2730&mod=lib-python.2.7.test.test_tcl A bient?t, Armin. From lac at openend.se Tue Jun 23 13:53:42 2015 From: lac at openend.se (Laura Creighton) Date: Tue, 23 Jun 2015 13:53:42 +0200 Subject: [pypy-dev] Final CFP: 2015 Workshop on Exascale Multi/many Core Computing Systems (E-MuCoCoS) (fwd) Message-ID: <201506231153.t5NBrgqI003844@fido.openend.se> This showed up in python-list, of all places, apparantly posted to comp.lang.python In case somebody wants to go to Portugal in September. Note: I am still a little hazy on what Exascale means, and therefore if we do it. :) Laura ------- Forwarded Message From: SP Injection-Date: Tue, 23 Jun 2015 09:51:23 +0000 To: python-list at python.org CALL FOR PAPERS 2015 Workshop on Exascale Multi/many Core Computing Systems (E-MuCoCoS) - - Paper submission deadline: June 30, 2015 (firm deadline) - - Workshop proceedings are published by the IEEE * CONTEXT Exascale computing will revolutionize computational science and engineering by providing 1000x the capabilities of currently available computing systems, while having a similar power footprint. The HPC community is working towards the development of the first Exaflop computer (expected around 2020) after reaching the Petaflop milestone in 2008. There are concerns that computer designs based on existing multi-core and many-core solutions will not scale to Exascale considering technical challenges (such as, productivity, energy consumption or reliability) and reasonable economic constraints. Therefore, novel multi-core and many-core solutions are required to reach Exascale. E-MuCoCoS will be organized in conjunction with the 18th IEEE Conference on Computational Science and Engineering (CSE 2015), Porto, Portugal, October 21 - 23, 2015. Previous editions of MuCoCoS workshop include: MuCoCoS 2014 (Porto, PT), MuCoCoS 2013 (Edinburgh, UK), MuCoCoS 2012 (SLC, US), MuCoCoS 2011 (Seoul, KR), MuCoCoS 2010 (Krakow, PL), MuCoCoS 2009 (Fukuoka, JP), MuCoCoS 2008 (Barcelona, ES). * TOPICS OF INTEREST E-MuCoCoS focuses on multi/many core languages, system software and architectural solutions towards Exascale computing systems. The topics of the workshop include but are not limited to: :: Methods and tools for preparing applications for Exascale :: Programming models, languages, libraries and compilation techniques :: Run-time systems and hardware support :: Patterns, algorithms and data structures :: Performance analysis, modeling, optimization and tuning * SUBMISSION GUIDELINES - - The papers should be prepared using the IEEE format, and no longer than 6 pages. Submitted papers will be carefully evaluated based on originality, significance to workshop topics, technical soundness, and presentation quality. - - Submission of the paper implies that should the paper be accepted, at least one of the authors will register and present the paper at the workshop. - - Please submit your paper (as PDF) electronically using the online submission system https://easychair.org/conferences/?conf=emucocos2015 * IMPORTANT DATES - - Submission: June 30, 2015 (firm deadline) - - Notification: July 28, 2015 - - Camera ready: September 4, 2015 - - Registration: September 4, 2015 - - Workshop: October 20, 2015 * PROGRAM COMMITTEE - - Erika Abraham, RWTH Aachen University (DE) - - Siegfried Benkner, University of Vienna (AT) - - Eduardo Cesar, UAB (ES) - - Jiri Dokulil, University of Vienna, (AT) - - Norbert Eicker, J?lich Supercomputing Centre (DE) - - Franz Franchetti, Carnegie Mellon University (US) - - Samir Genaim, Universidad Complutense de Madrid (ES) - - Houcine Hassan, Universitat Politecnica de Valencia, (ES) - - Atsushi Hori, RIKEN AICS (JP) - - Einar Broch Johnsen, University of Oslo, (NO) - - Christos Kartsaklis, Oak Ridge National Laboratory (US) - - J?rg Keller, FernUniversit?t in Hagen (DE) - - Christoph Kessler, Link?ping University (SE) - - Joanna Kolodziej, Cracow University of Technology (PL) - - Ivan Kondov, Karlsruhe Institute of Technology (DE) - - Erwin Laure, KTH/PDC (SE) - - Renato Miceli, SENAI CIMATEC (BR) - - Lasse Natvig, Norwegian University of Science and Technology (NO) - - Dana Petcu, West University of Timisoara (RO) - - Uwe Schwiegelshohn, TU Dortmund University (DE) - - Achim Streit, Karlsruhe Institute for Technology (DE) - - Osamu Tatebe, University of Tsukuba, (JP) - - Josef Weidendorfer, TUM (DE) * WORKSHOP CHAIR - - Sabri Pllana, Linnaeus University, Sweden http://homepage.lnu.se/staff/saplaa/ - -- https://mail.python.org/mailman/listinfo/python-list ------- End of Forwarded Message From lockhart at csl.cornell.edu Tue Jun 23 16:41:05 2015 From: lockhart at csl.cornell.edu (Derek Lockhart) Date: Tue, 23 Jun 2015 10:41:05 -0400 Subject: [pypy-dev] Final CFP: 2015 Workshop on Exascale Multi/many Core Computing Systems (E-MuCoCoS) (fwd) In-Reply-To: <201506231153.t5NBrgqI003844@fido.openend.se> References: <201506231153.t5NBrgqI003844@fido.openend.se> Message-ID: Exascale (super)computers are aiming for a performance target that exceeds 1 exaFLOPS, or 10**18 floating point ops per second. In the US this goal usually comes associated with a power requirement as well, I think last I heard the power goal was a cap of 20 megawatts (as proposed by the Dept. of Energy). Achieving exascale compute performance in a 20MW power envelope is impossible to achieve with conventional CPU architectures, so the challenges here are all about making compute/data transfer more efficient, effectively mapping computations to these large systems, etc. An interesting but slightly old paper with NVIDIA Research's perspective on the problem and their proposal to tackle it can be found here: - http://www.cs.nyu.edu/courses/spring12/CSCI-GA.3033-012/ieee-micro-echelon.pdf In the US, a number of interesting companies are working on exascale research: - https://asc.llnl.gov/fastforward/index.php On Tue, Jun 23, 2015 at 7:53 AM, Laura Creighton wrote: > This showed up in python-list, of all places, apparantly posted to > comp.lang.python > > In case somebody wants to go to Portugal in September. > > Note: I am still a little hazy on what Exascale means, and therefore > if we do it. :) > > Laura > > ------- Forwarded Message > > From: SP > Injection-Date: Tue, 23 Jun 2015 09:51:23 +0000 > > To: python-list at python.org > > CALL FOR PAPERS > > 2015 Workshop on Exascale Multi/many Core Computing Systems (E-MuCoCoS) > > - - Paper submission deadline: June 30, 2015 (firm deadline) > - - Workshop proceedings are published by the IEEE > > > * CONTEXT > > Exascale computing will revolutionize computational science and > engineering by providing 1000x the capabilities of currently available > computing systems, while having a similar power footprint. The HPC > community is working towards the development of the first Exaflop > computer (expected around 2020) after reaching the Petaflop milestone > in 2008. There are concerns that computer designs based on existing > multi-core and many-core solutions will not scale to Exascale > considering technical challenges (such as, productivity, energy > consumption or reliability) and reasonable economic constraints. > Therefore, novel multi-core and many-core solutions are required to > reach Exascale. > > E-MuCoCoS will be organized in conjunction with the 18th IEEE > Conference on Computational Science and Engineering (CSE 2015), Porto, > Portugal, October 21 - 23, 2015. > > Previous editions of MuCoCoS workshop include: MuCoCoS 2014 (Porto, > PT), MuCoCoS 2013 (Edinburgh, UK), MuCoCoS 2012 (SLC, US), MuCoCoS > 2011 (Seoul, KR), MuCoCoS 2010 (Krakow, PL), MuCoCoS 2009 (Fukuoka, > JP), MuCoCoS 2008 (Barcelona, ES). > > * TOPICS OF INTEREST > > E-MuCoCoS focuses on multi/many core languages, system software and > architectural solutions towards Exascale computing systems. The topics > of the workshop include but are not limited to: > > :: Methods and tools for preparing applications for Exascale > :: Programming models, languages, libraries and compilation techniques > :: Run-time systems and hardware support > :: Patterns, algorithms and data structures > :: Performance analysis, modeling, optimization and tuning > > * SUBMISSION GUIDELINES > > - - The papers should be prepared using the IEEE format, and no longer > than 6 pages. Submitted papers will be carefully evaluated based on > originality, significance to workshop topics, technical soundness, and > presentation quality. > - - Submission of the paper implies that should the paper be accepted, > at least one of the authors will register and present the paper at the > workshop. > - - Please submit your paper (as PDF) electronically using the online > submission system https://easychair.org/conferences/?conf=emucocos2015 > > * IMPORTANT DATES > > - - Submission: June 30, 2015 (firm deadline) > - - Notification: July 28, 2015 > - - Camera ready: September 4, 2015 > - - Registration: September 4, 2015 > - - Workshop: October 20, 2015 > > > * PROGRAM COMMITTEE > > - - Erika Abraham, RWTH Aachen University (DE) > - - Siegfried Benkner, University of Vienna (AT) > - - Eduardo Cesar, UAB (ES) > - - Jiri Dokulil, University of Vienna, (AT) > - - Norbert Eicker, J?lich Supercomputing Centre (DE) > - - Franz Franchetti, Carnegie Mellon University (US) > - - Samir Genaim, Universidad Complutense de Madrid (ES) > - - Houcine Hassan, Universitat Politecnica de Valencia, (ES) > - - Atsushi Hori, RIKEN AICS (JP) > - - Einar Broch Johnsen, University of Oslo, (NO) > - - Christos Kartsaklis, Oak Ridge National Laboratory (US) > - - J?rg Keller, FernUniversit?t in Hagen (DE) > - - Christoph Kessler, Link?ping University (SE) > - - Joanna Kolodziej, Cracow University of Technology (PL) > - - Ivan Kondov, Karlsruhe Institute of Technology (DE) > - - Erwin Laure, KTH/PDC (SE) > - - Renato Miceli, SENAI CIMATEC (BR) > - - Lasse Natvig, Norwegian University of Science and Technology (NO) > - - Dana Petcu, West University of Timisoara (RO) > - - Uwe Schwiegelshohn, TU Dortmund University (DE) > - - Achim Streit, Karlsruhe Institute for Technology (DE) > - - Osamu Tatebe, University of Tsukuba, (JP) > - - Josef Weidendorfer, TUM (DE) > > > * WORKSHOP CHAIR > > - - Sabri Pllana, Linnaeus University, Sweden > http://homepage.lnu.se/staff/saplaa/ > > - -- > https://mail.python.org/mailman/listinfo/python-list > > ------- End of Forwarded Message > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Wed Jun 24 00:08:48 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Wed, 24 Jun 2015 00:08:48 +0200 Subject: [pypy-dev] rogue CFFI speedups #....@k....$...# In-Reply-To: References: Message-ID: 2015-06-19 17:12 GMT+02:00 anatoly techtonik : > Hi, > > Just wanted to let you know of awesome 3x > speedup after python-tdl was ported to CFFI. > Thanks for sharing! Yes, CFFI is awsesome. > > python-tdl is a libtcod binding for Python. > > The wrapped libtcod is the very rad ?Doryen Library" > used to build roguelikes in C world. I am sure that > having it in Python will pave a road to more pleasant > text mode interfaces. =) > > There were some issues during the porting and > packaging process. I think you might be interested > to check them out: > > https://github.com/HexDecimal/python-tdl/issues/5 > > -- > anatoly t. > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Wed Jun 24 14:09:18 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Wed, 24 Jun 2015 14:09:18 +0200 Subject: [pypy-dev] tkinter tests broken In-Reply-To: References: Message-ID: Thanks Armin, 2015-06-23 9:48 GMT+02:00 Armin Rigo : > Hi Amaury, > > On 21 June 2015 at 14:11, Amaury Forgeot d'Arc wrote: > > 2015-06-21 12:33 GMT+02:00 Armin Rigo : > >> Can you fix the situation? Thanks! > > > > Should be fixed with 6453697f3a30. > > Thanks for fixing half of the failures :-) However, the other half > still remains: > http://buildbot.pypy.org/summary/longrepr?testname=unmodified&builder=pypy-c-jit-linux-x86-32&build=2730&mod=lib-python.2.7.test.test_tcl This is now fixed (with 9fa66d2aa78b): http://buildbot.pypy.org/summary?category=linux32&branch=%3Ctrunk%3E&recentrev=78278:9fa66d2aa78b -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From lac at openend.se Wed Jun 24 22:58:25 2015 From: lac at openend.se (lac at openend.se) Date: Wed, 24 Jun 2015 22:58:25 +0200 Subject: [pypy-dev] [PSF-Board-Public] PSF Meeting Minutes - 2015-06-08 (fwd) Message-ID: <201506242058.t5OKwPQ8027025@fido.openend.se> ------- Forwarded Message I've trimmed the minutes. Return-Path: Received: from mail.python.org (mail.python.org [82.94.164.166]) From: Diana Clarke To: Public PSF Board List , PSF Members List Subject: [PSF-Board-Public] PSF Meeting Minutes - 2015-06-08 Hi folks: The first PSF board meeting for the 2015/2016 term was held on June 8, 2015. Those meeting minutes can be found here: https://www.python.org/psf/records/board/minutes/2015-06-08/ The PSF also formally recognized the Scientific Python Working Group. More information about the working group can be found here: https://wiki.python.org/psf/ScientificWG https://pyfound.blogspot.com/2015/05/psfnumfocus-joint-working-group-on.html For more updates from the PSF, please check out our blog and follow us on Twitter. https://twitter.com/ThePSF https://pyfound.blogspot.com/ Cheers, - --diana _______________________________________________ PSF-Board-Public mailing list PSF-Board-Public at python.org https://mail.python.org/mailman/listinfo/psf-board-public ------- End of Forwarded Message Do we have any presence in that wg? We should probably have somebody be a member just to be on top of what the PSF, at any rate, thinks is scientific python .... Laura From phyo.arkarlwin at gmail.com Wed Jun 24 23:20:11 2015 From: phyo.arkarlwin at gmail.com (Phyo Arkar) Date: Thu, 25 Jun 2015 03:50:11 +0630 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? In-Reply-To: References: Message-ID: What do you guys think about skipping directly to pythin 3.5 and release it in-time when it releases? On Fri, Jun 5, 2015 at 2:05 PM, Armin Rigo wrote: > Hi Donald, hi everybody, > > On 1 June 2015 at 22:00, Donald Stufft wrote: > > So out of someone complaining about PyPy's lack of an up to date port of > > Python 3, it struck me that for someone just now looking into PyPy it > looks > > like PyPy is sitting on almost 60k USD in order to port PyPy3 from 3.2 > to 3.4. > > However the reality (via fijall) is that most of it, roughly 50k has > already > > been spent going from nothing to 3.2. > > Thanks for bringing this up. I added to pypy.org the display of the > amount left in our account for each project. > > Like the amount received, this number is updated from a source that > depends on a manual step somewhere. This manual step is typically > done only a few times per month. Don't be surprised if you donate and > it does not show up immediately! > > Current situation: > > numpy: $52184 received, $15999 left > py3k: $59578 received, $5045 left > stm (2nd call): $29112 received, $22016 left > > We also have two Summer of Code projects, one related to numpy > (performance via vectorization, not general compatibility) and one on > py3k (planning a first 3.3 version by midterm, but knowing that 3.4 is > the version most used, trying to push forward). STM is progressing > too, but I am alone on consuming the funds and recently I've been > "side-tracked" by CFFI 1.0 (coming back to STM now). > > > A bient?t, > > Armin. > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amauryfa at gmail.com Thu Jun 25 01:10:04 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Thu, 25 Jun 2015 01:10:04 +0200 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? In-Reply-To: References: Message-ID: 2015-06-24 23:20 GMT+02:00 Phyo Arkar : > What do you guys think about skipping directly to pythin 3.5 and release > it in-time when it releases? > Yes, it would be great to release 3.5 at the same time as CPython, but skipping releases won't make it faster. There are so many features to implement, many new modules. At least intermediate releases (3.3 and 3.4) make stable consistent milestones. Currently I'm kind of blocked on finishing the "more-rposix" branch (needed for the recent expansion of the posix module: os.supports_dir_fd...) It has still some failures: win32 does not translate, for example. Since it's mostly changes in rpython/ I wanted to make it land in the "default" branch first, but I'll probably move along and merge it into the py3.3 branch. > > On Fri, Jun 5, 2015 at 2:05 PM, Armin Rigo wrote: > >> Hi Donald, hi everybody, >> >> On 1 June 2015 at 22:00, Donald Stufft wrote: >> > So out of someone complaining about PyPy's lack of an up to date port of >> > Python 3, it struck me that for someone just now looking into PyPy it >> looks >> > like PyPy is sitting on almost 60k USD in order to port PyPy3 from 3.2 >> to 3.4. >> > However the reality (via fijall) is that most of it, roughly 50k has >> already >> > been spent going from nothing to 3.2. >> >> Thanks for bringing this up. I added to pypy.org the display of the >> amount left in our account for each project. >> >> Like the amount received, this number is updated from a source that >> depends on a manual step somewhere. This manual step is typically >> done only a few times per month. Don't be surprised if you donate and >> it does not show up immediately! >> >> Current situation: >> >> numpy: $52184 received, $15999 left >> py3k: $59578 received, $5045 left >> stm (2nd call): $29112 received, $22016 left >> >> We also have two Summer of Code projects, one related to numpy >> (performance via vectorization, not general compatibility) and one on >> py3k (planning a first 3.3 version by midterm, but knowing that 3.4 is >> the version most used, trying to push forward). STM is progressing >> too, but I am alone on consuming the funds and recently I've been >> "side-tracked" by CFFI 1.0 (coming back to STM now). >> >> >> A bient?t, >> >> Armin. >> _______________________________________________ >> pypy-dev mailing list >> pypy-dev at python.org >> https://mail.python.org/mailman/listinfo/pypy-dev >> > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > > -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Thu Jun 25 09:11:39 2015 From: arigo at tunes.org (Armin Rigo) Date: Thu, 25 Jun 2015 09:11:39 +0200 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? In-Reply-To: References: Message-ID: Hi Amaury, On 25 June 2015 at 01:10, Amaury Forgeot d'Arc wrote: > Currently I'm kind of blocked on finishing the "more-rposix" branch > (needed for the recent expansion of the posix module: os.supports_dir_fd...) > It has still some failures: win32 does not translate, for example. > Since it's mostly changes in rpython/ I wanted to make it land in the > "default" branch first, > but I'll probably move along and merge it into the py3.3 branch. If it's only adding new functions, then I think it's fine to merge it to default even if some of these functions cause translation errors on Windows. The default pypy won't call them anyway. A bient?t, Armin. From amauryfa at gmail.com Thu Jun 25 09:50:31 2015 From: amauryfa at gmail.com (Amaury Forgeot d'Arc) Date: Thu, 25 Jun 2015 09:50:31 +0200 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? In-Reply-To: References: Message-ID: 2015-06-25 9:11 GMT+02:00 Armin Rigo : > Hi Amaury, > > On 25 June 2015 at 01:10, Amaury Forgeot d'Arc wrote: > > Currently I'm kind of blocked on finishing the "more-rposix" branch > > (needed for the recent expansion of the posix module: > os.supports_dir_fd...) > > It has still some failures: win32 does not translate, for example. > > Since it's mostly changes in rpython/ I wanted to make it land in the > > "default" branch first, > > but I'll probably move along and merge it into the py3.3 branch. > > If it's only adding new functions, then I think it's fine to merge it > to default even if some of these functions cause translation errors on > Windows. The default pypy won't call them anyway. > No, this branch is actually a full rewrite of the ll_os.py file, all the code has been moved to rposix.py. The code is much simpler (no lazy registering callback function), and we have a consistent way to add new wrapper to C functions, even if they don't map to any 2.7 feature. -- Amaury Forgeot d'Arc -------------- next part -------------- An HTML attachment was scrubbed... URL: From hengha.mao at gmail.com Thu Jun 25 12:34:57 2015 From: hengha.mao at gmail.com (Yicong Huang) Date: Thu, 25 Jun 2015 18:34:57 +0800 Subject: [pypy-dev] pypy blocked at RPyGilAcquire () Message-ID: Hi, We embedded Pypy in C++ code, and found out if Pypy was initialized twice it would block at function RpyGilAcquire(). Here is the case: rpython_startup_code(); res = pypy_setup_home("...") res = pypy_execute_source_ptr(...) //Some code here rpython_startup_code(); res = pypy_setup_home("...") res = pypy_execute_source_ptr(...) We found pypy blocked at second pypy_execute_source_pty(...), the detail call stack are #0 0x0000003fea40b1c0 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f8543087a1d in RPyGilAcquire () from /usr/ali/odps-pypy/libpypy-c.so #2 0x00007f85425a5f8d in pypy_g_pypy_execute_source_ptr () from /usr/ali/odps-pypy/libpypy-c.so #3 0x00007f85423a6743 in pypy_execute_source_ptr () from /usr/ali/odps-pypy/libpypy-c.so The reason that we initialized pypy twice is that we would like to get a clean environment to execute without any global variables' pollution from the first run. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fijall at gmail.com Thu Jun 25 19:44:08 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Thu, 25 Jun 2015 19:44:08 +0200 Subject: [pypy-dev] For Donations, List How Much is Left (or Spent)? In-Reply-To: References: Message-ID: I can help you to iron out issue tomorrow I guess? On Thu, Jun 25, 2015 at 9:50 AM, Amaury Forgeot d'Arc wrote: > 2015-06-25 9:11 GMT+02:00 Armin Rigo : >> >> Hi Amaury, >> >> On 25 June 2015 at 01:10, Amaury Forgeot d'Arc wrote: >> > Currently I'm kind of blocked on finishing the "more-rposix" branch >> > (needed for the recent expansion of the posix module: >> > os.supports_dir_fd...) >> > It has still some failures: win32 does not translate, for example. >> > Since it's mostly changes in rpython/ I wanted to make it land in the >> > "default" branch first, >> > but I'll probably move along and merge it into the py3.3 branch. >> >> If it's only adding new functions, then I think it's fine to merge it >> to default even if some of these functions cause translation errors on >> Windows. The default pypy won't call them anyway. > > > No, this branch is actually a full rewrite of the ll_os.py file, > all the code has been moved to rposix.py. > > The code is much simpler (no lazy registering callback function), > and we have a consistent way to add new wrapper to C functions, > even if they don't map to any 2.7 feature. > > > -- > Amaury Forgeot d'Arc > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > From fijall at gmail.com Thu Jun 25 19:48:01 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Thu, 25 Jun 2015 19:48:01 +0200 Subject: [pypy-dev] pypy blocked at RPyGilAcquire () In-Reply-To: References: Message-ID: so far you can't do it (initialize pypy twice), we can maybe think about supporting it (and e.g. have interpreter instances) but it's quite some work. Generally speaking, we don't guarantee you any isolation (but you're free to execute stuff in your own namespace anyway,. but stuff like sys.modules etc. won't be cleaned for you) On Thu, Jun 25, 2015 at 12:34 PM, Yicong Huang wrote: > Hi, > > We embedded Pypy in C++ code, and found out if Pypy was initialized twice it > would block at function RpyGilAcquire(). > Here is the case: > > rpython_startup_code(); > res = pypy_setup_home("...") > res = pypy_execute_source_ptr(...) > //Some code here > rpython_startup_code(); > res = pypy_setup_home("...") > res = pypy_execute_source_ptr(...) > > We found pypy blocked at second pypy_execute_source_pty(...), the detail > call stack are > #0 0x0000003fea40b1c0 in pthread_cond_timedwait@@GLIBC_2.3.2 () from > /lib64/libpthread.so.0 > #1 0x00007f8543087a1d in RPyGilAcquire () from > /usr/ali/odps-pypy/libpypy-c.so > #2 0x00007f85425a5f8d in pypy_g_pypy_execute_source_ptr () from > /usr/ali/odps-pypy/libpypy-c.so > #3 0x00007f85423a6743 in pypy_execute_source_ptr () from > /usr/ali/odps-pypy/libpypy-c.so > > The reason that we initialized pypy twice is that we would like to get a > clean environment to execute without any global variables' pollution from > the first run. > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > From wlavrijsen at lbl.gov Thu Jun 25 19:55:41 2015 From: wlavrijsen at lbl.gov (wlavrijsen at lbl.gov) Date: Thu, 25 Jun 2015 10:55:41 -0700 (PDT) Subject: [pypy-dev] Final CFP: 2015 Workshop on Exascale Multi/many Core Computing Systems (E-MuCoCoS) (fwd) In-Reply-To: <201506231153.t5NBrgqI003844@fido.openend.se> References: <201506231153.t5NBrgqI003844@fido.openend.se> Message-ID: Hi Laura, On Tuesday 2015-06-23 13:53, Laura Creighton wrote: > Note: I am still a little hazy on what Exascale means, and therefore > if we do it. :) technically, I work on both: Cori (>28 petaflops) and cppyy for PyPy. Intermittently anyway; time is always limited ... But unless Python is the driver only, it won't do much good as any current design requires multi-threading as well as multi-processing, so the GIL is a domper. Best regards, Wim -- WLavrijsen at lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net From admalledd at gmail.com Thu Jun 25 20:07:29 2015 From: admalledd at gmail.com (Eric Driggers) Date: Thu, 25 Jun 2015 11:07:29 -0700 Subject: [pypy-dev] pypy blocked at RPyGilAcquire () In-Reply-To: References: Message-ID: Ran into a similar concept concern while doing some proof of concept work for my company. The approach that looked the most promising/easiest for a clean pypy state (both rpython internal and python globals) was to embed the sandbox controller and have it call out/create a new sandbox for each unit of isolated code. Although if you control the python code, reworking it such that it does not share global state is perhaps the best idea. On Thu, Jun 25, 2015 at 10:48 AM, Maciej Fijalkowski wrote: > so far you can't do it (initialize pypy twice), we can maybe think > about supporting it (and e.g. have interpreter instances) but it's > quite some work. Generally speaking, we don't guarantee you any > isolation (but you're free to execute stuff in your own namespace > anyway,. but stuff like sys.modules etc. won't be cleaned for you) > > On Thu, Jun 25, 2015 at 12:34 PM, Yicong Huang > wrote: > > Hi, > > > > We embedded Pypy in C++ code, and found out if Pypy was initialized > twice it > > would block at function RpyGilAcquire(). > > Here is the case: > > > > rpython_startup_code(); > > res = pypy_setup_home("...") > > res = pypy_execute_source_ptr(...) > > //Some code here > > rpython_startup_code(); > > res = pypy_setup_home("...") > > res = pypy_execute_source_ptr(...) > > > > We found pypy blocked at second pypy_execute_source_pty(...), the detail > > call stack are > > #0 0x0000003fea40b1c0 in pthread_cond_timedwait@@GLIBC_2.3.2 () from > > /lib64/libpthread.so.0 > > #1 0x00007f8543087a1d in RPyGilAcquire () from > > /usr/ali/odps-pypy/libpypy-c.so > > #2 0x00007f85425a5f8d in pypy_g_pypy_execute_source_ptr () from > > /usr/ali/odps-pypy/libpypy-c.so > > #3 0x00007f85423a6743 in pypy_execute_source_ptr () from > > /usr/ali/odps-pypy/libpypy-c.so > > > > The reason that we initialized pypy twice is that we would like to get a > > clean environment to execute without any global variables' pollution from > > the first run. > > > > _______________________________________________ > > pypy-dev mailing list > > pypy-dev at python.org > > https://mail.python.org/mailman/listinfo/pypy-dev > > > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From arigo at tunes.org Thu Jun 25 22:57:24 2015 From: arigo at tunes.org (Armin Rigo) Date: Thu, 25 Jun 2015 22:57:24 +0200 Subject: [pypy-dev] pypy blocked at RPyGilAcquire () In-Reply-To: References: Message-ID: Hi Maciej, On 25 June 2015 at 19:48, Maciej Fijalkowski wrote: > so far you can't do it (initialize pypy twice), we can maybe think > about supporting it (and e.g. have interpreter instances) but it's > quite some work. This might be what you have in mind, but note that this case could be supported generically from RPython (without hacking at the PyPy source): when the RPython program starts, simply copy all global variables. I think that this would also make a copy of the JIT and the GC. For example, the GC is controlled mostly by a prebuilt IncrementalMiniMarkGC instance, which is a global variable. It's actually very easy to do (it's done in STM for example) but at the cost of one extra indirection for every prebuilt constant access. Trying to reduce this cost is more challenging (but on the other hand probably too small to measure anyway). A bient?t, Armin. From ozancag at gmail.com Mon Jun 29 15:02:23 2015 From: ozancag at gmail.com (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Mon, 29 Jun 2015 15:02:23 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython Message-ID: Hi, I just downloaded PyPy 2.6.0 just to play with it. I have a simple line-by-line file reading example where the file is 324MB. Code: # Not doing this import crashes PyPy with MemoryError?? from io import open a = 0 f = open(fname) for line in f.readlines(): a += len(line) f.close() PyPy: Python 2.7.9 (295ee98b69288471b0fcf2e0ede82ce5209eb90b, Jun 01 2015, 17:30:13) [PyPy 2.6.0 with GCC 4.9.2] on linux2 real 0m6.068s user 0m4.582s sys 0m0.846s CPython (2.7.10) real 0m3.799s user 0m2.851s sys 0m0.860s Am I doing something wrong or is this expected? Thanks! -- Ozan ?a?layan Research Assistant Galatasaray University - Computer Engineering Dept. http://www.ozancaglayan.com From ozancag at gmail.com Mon Jun 29 15:11:41 2015 From: ozancag at gmail.com (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Mon, 29 Jun 2015 15:11:41 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: Message-ID: I found this: https://bitbucket.org/pypy/pypy/issue/729/ I did an strace test and both CPython and PyPy do read syscalls with chunks of 4096. From oscar.j.benjamin at gmail.com Mon Jun 29 15:49:20 2015 From: oscar.j.benjamin at gmail.com (Oscar Benjamin) Date: Mon, 29 Jun 2015 13:49:20 +0000 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: Message-ID: On Mon, 29 Jun 2015 at 14:44 Oscar Benjamin wrote: With your code (although I didn't import io.open) I found the timings: > CPython 2.7: 1.4s > PyPy 2.7: 2.3s > > I changed it to > for line in f: # (not f.readlines()) > a += len(line) > > With that change I get: > CPython 2.7: 1.3s > PyPy 2.7: 0.6s > > Note that all of the timings above are "warm cache". That means that the file was already cached in memory by the operating system because I had recently read/written it. The time taken to load the file cold cache (e.g. after rebooting) would probably be much longer in all cases so that the difference between PyPy and CPython would not be significant. The problem you've posted should really be IO bound which isn't really the kind of situation where PyPy gains you much speed over CPython. -- Oscar -------------- next part -------------- An HTML attachment was scrubbed... URL: From oscar.j.benjamin at gmail.com Mon Jun 29 15:44:33 2015 From: oscar.j.benjamin at gmail.com (Oscar Benjamin) Date: Mon, 29 Jun 2015 13:44:33 +0000 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: Message-ID: On Mon, 29 Jun 2015 at 14:02 Ozan ?a?layan wrote: > Hi, > > I just downloaded PyPy 2.6.0 just to play with it. > > > I have a simple line-by-line file reading example where the file is 324MB. > > Code: > > # Not doing this import crashes PyPy with MemoryError?? > from io import open > > a = 0 > f = open(fname) > for line in f.readlines(): > a += len(line) > f.close() > > PyPy: > Python 2.7.9 (295ee98b69288471b0fcf2e0ede82ce5209eb90b, Jun 01 2015, > 17:30:13) > [PyPy 2.6.0 with GCC 4.9.2] on linux2 > > real 0m6.068s > user 0m4.582s > sys 0m0.846s > > CPython (2.7.10) > > real 0m3.799s > user 0m2.851s > sys 0m0.860s > > Am I doing something wrong or is this expected? > I tested this with cpython 2.7 and pypy 2.7 and I found that it was 2x slower as you say. It seems that readlines() is somehow slower in pypy. You don't actually need to call readlines() in this case though and it's faster not to. With your code (although I didn't import io.open) I found the timings: CPython 2.7: 1.4s PyPy 2.7: 2.3s I changed it to for line in f: # (not f.readlines()) a += len(line) With that change I get: CPython 2.7: 1.3s PyPy 2.7: 0.6s So calling readlines() makes it slower in both CPython and PyPy. If you don't call readlines() then PyPy is 2x faster than CPython (at least on this machine). Probably also the reason for the MemoryError was that you are using readlines(). The reason for this is that readlines() reads all of the lines of the file into memory as a list of Python string objects. If you just loop over f directly then it reads the file one line at a time and so it requires much less memory. I don't know how much spare RAM you have but if you got MemoryError it suggests that you don't have enough to load the whole file into memory using readlines(). Note that even though this machine has 8GB if RAM (with over 7GB unused) and can load the file into memory quite comfortably I still wouldn't write code that assumed it was okay to load a 324MB file into memory unless there was some actual need to do that. -- Oscar -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozancag at gmail.com Mon Jun 29 15:54:58 2015 From: ozancag at gmail.com (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Mon, 29 Jun 2015 15:54:58 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: Message-ID: Hi, Oh It's my bad, I though that readlines iterates over the file, I'm always confusing this. But still the new results are interesting: time bin/pypy testfile.py 338695509 real 0m0.591s user 0m0.494s sys 0m0.096s time python testfile.py 338695509 real 0m0.560s user 0m0.495s sys 0m0.064s So PyPy is still a little slower here wrt to CPython. This is on warm cache too. Anyways, thanks for pointing out the readlines() stuff :) From rymg19 at gmail.com Mon Jun 29 15:57:08 2015 From: rymg19 at gmail.com (Ryan Gonzalez) Date: Mon, 29 Jun 2015 08:57:08 -0500 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: Message-ID: <90A47013-D59E-4C3F-849B-8C9B5E0A1BB2@gmail.com> Could you try just using: for line in f: ... That refrains from the loading the entire file into memory at once. On June 29, 2015 8:02:23 AM CDT, "Ozan ?a?layan" wrote: >Hi, > >I just downloaded PyPy 2.6.0 just to play with it. > > >I have a simple line-by-line file reading example where the file is >324MB. > >Code: > ># Not doing this import crashes PyPy with MemoryError?? >from io import open > >a = 0 >f = open(fname) >for line in f.readlines(): > a += len(line) >f.close() > >PyPy: >Python 2.7.9 (295ee98b69288471b0fcf2e0ede82ce5209eb90b, Jun 01 2015, >17:30:13) >[PyPy 2.6.0 with GCC 4.9.2] on linux2 > >real 0m6.068s >user 0m4.582s >sys 0m0.846s > >CPython (2.7.10) > >real 0m3.799s >user 0m2.851s >sys 0m0.860s > >Am I doing something wrong or is this expected? > >Thanks! > >-- >Ozan ?a?layan >Research Assistant >Galatasaray University - Computer Engineering Dept. >http://www.ozancaglayan.com >_______________________________________________ >pypy-dev mailing list >pypy-dev at python.org >https://mail.python.org/mailman/listinfo/pypy-dev -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -------------- next part -------------- An HTML attachment was scrubbed... URL: From fijall at gmail.com Mon Jun 29 15:58:12 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Mon, 29 Jun 2015 15:58:12 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: Message-ID: it's sort-of-known, we have a branch to try to address this, the main problem is that we try to do buffering ourselves as opposed to just use libc buffering, which turns out to be not as good. Sorry about that :/ On Mon, Jun 29, 2015 at 3:54 PM, Ozan ?a?layan wrote: > Hi, > > Oh It's my bad, I though that readlines iterates over the file, I'm > always confusing this. > > But still the new results are interesting: > > time bin/pypy testfile.py > 338695509 > > real 0m0.591s > user 0m0.494s > sys 0m0.096s > > time python testfile.py > 338695509 > > real 0m0.560s > user 0m0.495s > sys 0m0.064s > > So PyPy is still a little slower here wrt to CPython. This is on warm cache too. > > Anyways, thanks for pointing out the readlines() stuff :) > _______________________________________________ > pypy-dev mailing list > pypy-dev at python.org > https://mail.python.org/mailman/listinfo/pypy-dev From cfbolz at gmx.de Mon Jun 29 16:33:15 2015 From: cfbolz at gmx.de (Carl Friedrich Bolz) Date: Mon, 29 Jun 2015 16:33:15 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: Message-ID: <5591572B.8000000@gmx.de> Hi Ozan, in addition to what the others said of not using readlines in the first place: I actually discovered a relatively slow part in our file.readlines implementation and fixed it. The nightly build of tonight should improve the situation. Thanks for reporting this! Out of curiosity, what are you using PyPy for? Cheers, Carl Friedrich On 29/06/15 15:02, Ozan ?a?layan wrote: > Hi, > > I just downloaded PyPy 2.6.0 just to play with it. > > > I have a simple line-by-line file reading example where the file is 324MB. > > Code: > > # Not doing this import crashes PyPy with MemoryError?? > from io import open > > a = 0 > f = open(fname) > for line in f.readlines(): > a += len(line) > f.close() > > PyPy: > Python 2.7.9 (295ee98b69288471b0fcf2e0ede82ce5209eb90b, Jun 01 2015, 17:30:13) > [PyPy 2.6.0 with GCC 4.9.2] on linux2 > > real 0m6.068s > user 0m4.582s > sys 0m0.846s > > CPython (2.7.10) > > real 0m3.799s > user 0m2.851s > sys 0m0.860s > > Am I doing something wrong or is this expected? > > Thanks! > From fijall at gmail.com Mon Jun 29 16:44:44 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Mon, 29 Jun 2015 16:44:44 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: <20150629144302.GA8918@domone> References: <20150629144302.GA8918@domone> Message-ID: On Mon, Jun 29, 2015 at 4:43 PM, Ond?ej B?lka wrote: > On Mon, Jun 29, 2015 at 03:58:12PM +0200, Maciej Fijalkowski wrote: >> it's sort-of-known, we have a branch to try to address this, the main >> problem is that we try to do buffering ourselves as opposed to just >> use libc buffering, which turns out to be not as good. Sorry about >> that :/ >> > Do you have testcase to report? I could fix that. testcase of what? PyPy buffering not being up to scratch compared to libc buffering? From neleai at seznam.cz Mon Jun 29 16:43:02 2015 From: neleai at seznam.cz (=?utf-8?B?T25kxZllaiBCw61sa2E=?=) Date: Mon, 29 Jun 2015 16:43:02 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: Message-ID: <20150629144302.GA8918@domone> On Mon, Jun 29, 2015 at 03:58:12PM +0200, Maciej Fijalkowski wrote: > it's sort-of-known, we have a branch to try to address this, the main > problem is that we try to do buffering ourselves as opposed to just > use libc buffering, which turns out to be not as good. Sorry about > that :/ > Do you have testcase to report? I could fix that. From neleai at seznam.cz Mon Jun 29 16:56:07 2015 From: neleai at seznam.cz (=?utf-8?B?T25kxZllaiBCw61sa2E=?=) Date: Mon, 29 Jun 2015 16:56:07 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: <20150629144302.GA8918@domone> Message-ID: <20150629145607.GA9086@domone> On Mon, Jun 29, 2015 at 04:44:44PM +0200, Maciej Fijalkowski wrote: > On Mon, Jun 29, 2015 at 4:43 PM, Ond?ej B?lka wrote: > > On Mon, Jun 29, 2015 at 03:58:12PM +0200, Maciej Fijalkowski wrote: > >> it's sort-of-known, we have a branch to try to address this, the main > >> problem is that we try to do buffering ourselves as opposed to just > >> use libc buffering, which turns out to be not as good. Sorry about > >> that :/ > >> > > Do you have testcase to report? I could fix that. > > testcase of what? PyPy buffering not being up to scratch compared to > libc buffering? Why libc buffering is bad so it could be fixed. From fijall at gmail.com Mon Jun 29 16:58:40 2015 From: fijall at gmail.com (Maciej Fijalkowski) Date: Mon, 29 Jun 2015 16:58:40 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: <20150629145607.GA9086@domone> References: <20150629144302.GA8918@domone> <20150629145607.GA9086@domone> Message-ID: On Mon, Jun 29, 2015 at 4:56 PM, Ond?ej B?lka wrote: > On Mon, Jun 29, 2015 at 04:44:44PM +0200, Maciej Fijalkowski wrote: >> On Mon, Jun 29, 2015 at 4:43 PM, Ond?ej B?lka wrote: >> > On Mon, Jun 29, 2015 at 03:58:12PM +0200, Maciej Fijalkowski wrote: >> >> it's sort-of-known, we have a branch to try to address this, the main >> >> problem is that we try to do buffering ourselves as opposed to just >> >> use libc buffering, which turns out to be not as good. Sorry about >> >> that :/ >> >> >> > Do you have testcase to report? I could fix that. >> >> testcase of what? PyPy buffering not being up to scratch compared to >> libc buffering? > > Why libc buffering is bad so it could be fixed. no, libc buffering is good and we should use it as opposed to our home-grown solution which is bad and likely should be thrown away ;-) From ozancag at gmail.com Mon Jun 29 17:12:49 2015 From: ozancag at gmail.com (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Mon, 29 Jun 2015 17:12:49 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: <20150629144302.GA8918@domone> Message-ID: Hello all, Well I am searching my dream scientific language :) The current codebase that I am working with is related to a language translation software written in C++. I wanted to re-implement parts of it in Python and/or Julia to both learn it (as I didn't write the C++ stuff) and maybe to make it available for other people who are interested. I saw Pyston last night then I came back to PyPy. As a first step, I tried to parse a 300MB structed text file containing 1.1M lines like these: 0 ||| I love you mother . ||| label=number1 number2 number3 number4 label2=number5 number6 ... number19 ||| number20 Line-by-line accessing was actually pretty fast *but* trying to store the lines in a Python list drains RAM on my 4G laptop. This is disappointing. A raw text file (utf-8) of 300MB takes more than 1GB of memory. Today I went through pypy and did some benchmarks. Line parsing is as follows: - Split it from " ||| " - Convert 1st field to int and 4rd field to float. - Cleanup label= stuff from 2nd field using re.sub() - Append a dict(1) or a class(2) representing each line to a list. # Dict(1): # PyPy: ~1.4G RAM, ~12.7 seconds # CPython: ~1.2G RAM, 28.7 seconds # Class(2): # PyPy: ~1.2G, ~11.1 seconds # CPython: ~1.3G, ~32 seconds The memory measurements are not precise as I tracked them visually using top :) Attaching the code. I'm not an optimization guru, I'm pretty sure that there are suboptimal parts in the code. But the crucial part is memory complexity. Normally those text files are ~1GB on disk this means that I can't represent them in-memory with Python with this code. This is bad. Any suggestions? Thanks! -------------- next part -------------- A non-text attachment was scrubbed... Name: NBest.py Type: text/x-python Size: 2544 bytes Desc: not available URL: From neleai at seznam.cz Mon Jun 29 17:17:00 2015 From: neleai at seznam.cz (=?utf-8?B?T25kxZllaiBCw61sa2E=?=) Date: Mon, 29 Jun 2015 17:17:00 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: <20150629144302.GA8918@domone> <20150629145607.GA9086@domone> Message-ID: <20150629151700.GA11441@domone> On Mon, Jun 29, 2015 at 04:58:40PM +0200, Maciej Fijalkowski wrote: > On Mon, Jun 29, 2015 at 4:56 PM, Ond?ej B?lka wrote: > > On Mon, Jun 29, 2015 at 04:44:44PM +0200, Maciej Fijalkowski wrote: > >> On Mon, Jun 29, 2015 at 4:43 PM, Ond?ej B?lka wrote: > >> > On Mon, Jun 29, 2015 at 03:58:12PM +0200, Maciej Fijalkowski wrote: > >> >> it's sort-of-known, we have a branch to try to address this, the main > >> >> problem is that we try to do buffering ourselves as opposed to just > >> >> use libc buffering, which turns out to be not as good. Sorry about > >> >> that :/ > >> >> > >> > Do you have testcase to report? I could fix that. > >> > >> testcase of what? PyPy buffering not being up to scratch compared to > >> libc buffering? > > > > Why libc buffering is bad so it could be fixed. > > no, libc buffering is good and we should use it as opposed to our > home-grown solution which is bad and likely should be thrown away ;-) Ok, I wrongly parsed your sentence to mean that we do buffering ourself because libc one is bad. From oscar.j.benjamin at gmail.com Mon Jun 29 17:52:38 2015 From: oscar.j.benjamin at gmail.com (Oscar Benjamin) Date: Mon, 29 Jun 2015 15:52:38 +0000 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: <20150629144302.GA8918@domone> Message-ID: On Mon, 29 Jun 2015 at 16:13 Ozan ?a?layan wrote: > Hello all, > > Well I am searching my dream scientific language :) > > The current codebase that I am working with is related to a language > translation software written in C++. I wanted to re-implement parts of > it in Python and/or Julia to both learn it (as I didn't write the C++ > stuff) and maybe to make it available for other people who are > interested. > > I saw Pyston last night then I came back to PyPy. > > As a first step, I tried to parse a 300MB structed text file > containing 1.1M lines like these: > > 0 ||| I love you mother . ||| label=number1 number2 number3 number4 > label2=number5 number6 ... number19 ||| number20 > > Line-by-line accessing was actually pretty fast *but* trying to store > the lines in a Python list drains RAM on my 4G laptop. This is > disappointing. A raw text file (utf-8) of 300MB takes more than 1GB of > memory. > The first question is always: can you avoid storing everything in memory? There are improvements you could do but you'll still hit the memory limit again with a slightly bigger file. So rethink that part of the code if possible. This is a fundamental algorithmic point: as long as your approach requires everything to be stored in memory it has an upper size limit. You can incrementally raise that limit with diminishing returns but it's usually better to think of a way to remove the upper limit altogether. You're storing a Python object for each line in the file. Each of these objects has an associated dict. That probably represents a significant part of the memory storage. Try using __slots__ which is intended for the situation where you have lots of small instances. (Not sure how much difference it makes with PyPy though). You can also get significantly better memory efficiency if you store using arrays of some kind rather than many different Python objects. I would probably use numpy record arrays for this problem. -- Oscar -------------- next part -------------- An HTML attachment was scrubbed... URL: From ozancag at gmail.com Mon Jun 29 21:40:38 2015 From: ozancag at gmail.com (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Mon, 29 Jun 2015 21:40:38 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: <20150629144302.GA8918@domone> Message-ID: Hi, Yes I thought of the evident question and I think I can avoid keeping everything in memory by doing two passes of the file. Regarding __slots__, it seemed to help using CPython but pypy + slots crashed/trashed in a very hardcore way :) From arigo at tunes.org Mon Jun 29 21:46:50 2015 From: arigo at tunes.org (Armin Rigo) Date: Mon, 29 Jun 2015 21:46:50 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: References: <20150629144302.GA8918@domone> Message-ID: Hi, On 29 June 2015 at 21:40, Ozan ?a?layan wrote: > Regarding __slots__, it seemed to help using CPython but pypy + slots > crashed/trashed in a very hardcore way :) __slots__ is mostly ignored in PyPy (it always compact instances as if they had slots). The crash/trash is probably due to some other issue. A bient?t, Armin. From lac at openend.se Mon Jun 29 22:26:54 2015 From: lac at openend.se (Laura Creighton) Date: Mon, 29 Jun 2015 22:26:54 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: Message from =?UTF-8?B?T3phbiDDh2HEn2xheWFu?= of "Mon, 29 Jun 2015 21:40:38 +0200." References: <20150629144302.GA8918@domone> Message-ID: <201506292026.t5TKQsWo012048@fido.openend.se> In a message of Mon, 29 Jun 2015 21:40:38 +0200, Ozan ?a?layan writes: >Hi, > >Yes I thought of the evident question and I think I can avoid keeping >everything in memory by doing two passes of the file. > >Regarding __slots__, it seemed to help using CPython but pypy + slots >crashed/trashed in a very hardcore way :) PyPy always compacts instances as if they had slots, so it should make no difference. If using it makes things crash, then we have a really horrible bug -- can you post the smallest code that provokes this? (Though my bet is that you have somehting else wrong, not the slots ...) Laura From ozancag at gmail.com Mon Jun 29 23:53:21 2015 From: ozancag at gmail.com (=?UTF-8?B?T3phbiDDh2HEn2xheWFu?=) Date: Mon, 29 Jun 2015 23:53:21 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: <201506292026.t5TKQsWo012048@fido.openend.se> References: <20150629144302.GA8918@domone> <201506292026.t5TKQsWo012048@fido.openend.se> Message-ID: Well I tried again but cant reproduce it. BTW cut down the whole code to 4 seconds with PyPy vs 28 seconds on CPython. The original C++ code might be slower than this, i'll check it. Thanks for fast replies, contributions, kindness :) -------------- next part -------------- An HTML attachment was scrubbed... URL: From lac at openend.se Tue Jun 30 00:10:41 2015 From: lac at openend.se (Laura Creighton) Date: Tue, 30 Jun 2015 00:10:41 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: Message from =?UTF-8?B?T3phbiDDh2HEn2xheWFu?= of "Mon, 29 Jun 2015 23:53:21 +0200." References: <20150629144302.GA8918@domone> <201506292026.t5TKQsWo012048@fido.openend.se> Message-ID: <201506292210.t5TMAfUb014770@fido.openend.se> In a message of Mon, 29 Jun 2015 23:53:21 +0200, Ozan ?a?layan writes: >Well I tried again but cant reproduce it. BTW cut down the whole code to 4 >seconds with PyPy vs 28 seconds on CPython. The original C++ code might be >slower than this, i'll check it. > >Thanks for fast replies, contributions, kindness :) You are welcome for the kindness. Try to encourage it wherever you go. So _very_ many things go better with kindness, and so many people think that it is in some way beneath them to be kind, to our great sorrow. Laura From hodgestar at gmail.com Tue Jun 30 01:21:28 2015 From: hodgestar at gmail.com (Simon Cross) Date: Tue, 30 Jun 2015 01:21:28 +0200 Subject: [pypy-dev] A simple file reading is 2x slow wrt CPython In-Reply-To: <201506292210.t5TMAfUb014770@fido.openend.se> References: <20150629144302.GA8918@domone> <201506292026.t5TKQsWo012048@fido.openend.se> <201506292210.t5TMAfUb014770@fido.openend.se> Message-ID: On Tue, Jun 30, 2015 at 12:10 AM, Laura Creighton wrote: > You are welcome for the kindness. Try to encourage it wherever you go. > So _very_ many things go better with kindness, and so many people think > that it is in some way beneath them to be kind, to our great sorrow. +1