Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New issue] zipimport does not correctly import submodules
2. [New comment] PYC - Allow the Setting of the Icon if generating EXE
3. [New comment] Visual Studio 2010 crashes when Iron Pyth
The short answer is yes :-) I think Jeff is working on this, we had lost
the nuget packaging file at one point but were able to retrieve it. Jeff
would be able to give you a better idea as to when and so forth.
On Fri, Feb 17, 2012 at 9:33 PM, Leo Carbajal wrote:
> Sorry to revive an old thread,
Thanks for your help, everyone.
The following appears to do what I asked for:
"""is64bit() returns boolean value of detected Python word size"""
def is64bit():
import sys
if sys.platform == 'cli': # IronPython
import System
return System.IntPtr.Size == 8
else: # CPyth
Yeah, the nuget packaging almost works again. It'll definitely be
updated for 2.7.2.
- Jeff
On Sat, Feb 18, 2012 at 7:37 AM, Slide wrote:
> The short answer is yes :-) I think Jeff is working on this, we had lost the
> nuget packaging file at one point but were able to retrieve it. Jeff would
>
IsWow64Process()
(http://msdn.microsoft.com/en-us/library/windows/desktop/ms684139(v=vs.85).aspx)
is the function you want, and you should be able to use ctypes to call
it from CPython and IronPython.
- Jeff
On Sat, Feb 18, 2012 at 8:42 AM, Vernon Cole wrote:
> Thanks for your help, everyone.
>
Hello,
I have a question about assemblies compiled with pyc.py. If you just name
them normally like, "Foobar.dll" or "Snafu.dll" you can add a reference
to them and import them into IronPython as one would expect. If however
you name them like "Foobar.Snafu.dll" you can add a reference to them
but
The import statement is used for namespaces, which usually (but don't have to)
match the assembly names. You reference the assembly once, and import whatever
types/namespaces you need from it. Thinking of it in another way, referencing
the assembly grants the ability to import from that assembly
Hi Keith,
Thanks for your response. I actually am familiar with python's import
statement as I have been
programming in python for years now :) I'm afraid I don't see how your
response answers my
question about dotted assembly names and python code compiled with pyc.py.
Could you maybe
clarify for
The point I was trying to make is that the assembly name (dots or no dots) has
nothing to do with the contents of the assembly. It is simply a unique moniker.
As far as I know, pyc.py emits the same MSIL into the resulting assembly no
matter what you name the final file. And the namespaces withi
