Re: [pypy-dev] py3k and py3.3 branches

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 Ga

Re: [pypy-dev] Working version of pypy3 that support Python 3.3

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?

Re: [pypy-dev] Working version of pypy3 that support Python 3.3

:: 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

Re: [pypy-dev] Working version of pypy3 that support Python 3.3

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

Re: [pypy-dev] Working version of pypy3 that support Python 3.3

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:

Re: [pypy-dev] Working version of pypy3 that support Python 3.3

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 Rach

Re: [pypy-dev] Working version of pypy3 that support Python 3.3

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

Re: [pypy-dev] Working version of pypy3 that support Python 3.3

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 te

[pypy-dev] Working version of pypy3 that support Python 3.3

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

Re: [pypy-dev] py3k and py3.3 branches

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 a

Re: [pypy-dev] Sandbox missing functions like 'fcntl'

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, benef

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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@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 tr

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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:

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

"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: >

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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,

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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 s

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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 mod

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

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 a

Re: [pypy-dev] How to use interperter level code from a module for app level code in another module

"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 lik