Also related to 30312 and version number issues in general - it looks like
sys.version_info should be updated to be 2.7.1.
> -Original Message-
> From: ironpython-users-bounces+dinov=microsoft@python.org
> [mailto:ironpython-users-bounces+dinov=microsoft@python.org] On
> Behalf Of
On 6/20/2011 11:53 AM, Jeff Hardy wrote:
Yes, but I think everyone chooses the same path you do
(rebuild/resign). At least, I'm pretty sure that's what Resolver One
does (I don't know of any other apps ... maybe we need a "Who's
Using?" page).
SharpDevelop does the same as well. Not to mention
On Mon, Jun 20, 2011 at 10:50 PM, Markus Schaber
wrote:
> Hi, Jeff,
>
>
> > For embedding, I would recommend you continue what you're doing - it's
> > just just straight-up safer. It's a shame zipimport doesn't work; we
> could
> > cut the deployed size of the stdlib down significantly.
>
> Hmm.
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] Chaining LINQ calls fails
2. [New comment] Chaining LINQ calls fails
3. [Status update] IronPython building against SL4 (from CodePlex)
4. [Status update] Internal changeset
