Hi Michael,<br>I started out on implementing this, but I am importing maybe a dozen of the std. library modules, which then import others, and so on. It appears that eventually, most of the std modules would have to be imported explicitly (perhaps 400 or so files) which might make for a somewhat cumbersome command line, incidentally also about 20K characters too long :-). I'm hoping to find a way to get this to work as well as it did under IP 2.5 / .NET 3.5.<br>
<br>Noah: what kind of problems are YOU having with pyc.py under 4.0? Maybe one of us can suggest something if we have an understanding of what you're trying to do.<br>Ken<br><br><div class="gmail_quote">On Wed, Oct 6, 2010 at 7:08 AM, Michael Foord <span dir="ltr"><<a href="mailto:michael@voidspace.org.uk">michael@voidspace.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"><div class="im">
On 05/10/2010 22:27, Ken MacDonald wrote:
<blockquote type="cite">I've been looking at the .exe's we built - using
pyc.py - with IP 2.5/.Net 3.5 and IP2.7 / .NET 4.0. In the 2.7
.exe, it appears that the imports (like "os") are not being built
into the .exe/.dll, but instead are required to be imported in
source form, e.g. "os.py" must be somewhere on sys.path. In the IP
2.5 .exe's we had been building, they would run fine on machines
without the IP standard library installed at all, in other words,
with "os.py" not present on the machine at all. We did notice that
the .exe in question went from being 2.9 MB in it's IP 2.5
incarnation, down to 1.2 MB in the IP 2.7 version, and the newer
version requires that the source code for the IP standard library
be on the path. Is this a deliberate change in behavior? We never
had to package the standard library source when we sent out .exe's
to customers before<br>
</blockquote>
<br></div>
Hmmm... I'm pretty sure I always had to explicitly compile and
bundle the standard library with previous versions of Python. Odd.
Anyway, the simple solution is to ensure that you add any standard
library modules you use to the set you compile and ship.<div><div></div><div class="h5"><br>
<br>
All the best,<br>
<br>
Michael Foord<br>
<br>
<br>
<blockquote type="cite">
<br>
>"os" is not an assembly but a Python module from the standard
library. You need to ensure >that the Python standard library
(or the parts that you use and their dependencies) is on the
>path.<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div bgcolor="#ffffff" text="#000000"> <br>
All the best,<br>
<br>
Michael Foord<br>
<br>
<blockquote type="cite">
<div> and how do I ensure it gets found from my
.exe - is there a specific env. variable, or the Windows
%PATH% e.v., or something I haven't AddReference'd
to????<br>
Thanks,<br>
Ken<br>
<br>
<br>
</div>
<pre><fieldset></fieldset>
_______________________________________________
Users mailing list
<div><a href="mailto:Users@lists.ironpython.com" target="_blank">Users@lists.ironpython.com</a>
<a href="http://lists.ironpython.com/listinfo.cgi/users-ironpython.com" target="_blank">http://lists.ironpython.com/listinfo.cgi/users-ironpython.com</a>
</div></pre>
</blockquote>
<br>
<br>
<pre cols="72">--
<a href="http://www.voidspace.org.uk/blog" target="_blank">http://www.voidspace.org.uk/blog</a>
READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
</pre>
</div>
</blockquote>
</div>
<br>
</blockquote>
<br>
<br>
<pre cols="72">--
<a href="http://www.voidspace.org.uk/blog" target="_blank">http://www.voidspace.org.uk/blog</a>
READ CAREFULLY. By accepting and reading this email you agree,
on behalf of your employer, to release me from all obligations
and waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
</pre>
</div></div></div>
</blockquote></div><br>