The PTVS release is really an extended version of the tools in IronPython 2.7.
It adds support for CPython including debugging, profiling, etc... while still
supporting IronPython as well. We'll likely either replace the tools
distributed w/ IronPython with this version (maybe minus things li
Patty wrote:
> Thanks so much for this reference - and the detailed further explanation! I
> have a Windows 7 system and recently installed Visual Studio 2010 for the
> SQL Server, Visual C/C++ and Visual Basic. I would love to have this Python
> tool installed under Visual Studio but a few que
Kirby wrote:
> ** Unconfirmed rumors about IronPython leave me blog searching this
> afternoon. Still part of Codeplex?
IronPython is still using CodePlex for bug tracking and posting releases but
active development is now on GitHub w/ a Mercurial mirror. Jeff's blog has
more info: http://jdha
Terry wrote:
> > IronPython targets Python 2.6.
>
> They plan to release a 2.7 version sometime this year after CPython2.7
> is released. They plan to release a 3.2 version early next year, soon
> after CPython. They should be able to do that because they already have
> a 3.1 version mostly done
In the ssl module docs (and in the tests) it says that if you have a client
specifying PROTOCOL_SSLv23 (so it'll use v2 or v3) and a server specifying
PROTOCOL_SSLv3 (so it'll only use v3) that you cannot connect between the two.
Why doesn't this end up using SSL v3 for the communication?
--
Steve wrote:
> id() simply returns a unique value identifying a particular object. In
> CPython, where objects do not migrate in memory once created, the
> memory
> address of the object is used. In IronPython each object is assigned an
> id when it is created, and that value is stored as an attrib
Stefan wrote:
> >From an implementors point of view, it's actually quite the opposite. Most
> syntax features of Python 3 can be easily implemented on top of an existing
> Py2 Implementation (we have most of them in Cython already, and I really
> found them fun to write), and the shifting-around in
Lev wrote:
> I'm an on and off Python developer and use it as one of the tools.
> Never for writing "full-blown" applications, but rather small, "one-of-
> a-kind" utilities. This time I needed some sort of backup and
> reporting utility, which is to be used by the members of our team
> once or twi
Dirkjan Ochtman wrote:
>
> It would seem to me that optimizations are likely to require data
> structure changes, for exactly the kind of core data structures that
> you're talking about locking down. But that's just a high-level view,
> I might be wrong.
>
In particular I would guess that ref co
instructions, once it's known what the values of
the variables are that are the operands. The trade-off is compilation
time + type checks + stub look-up.
What I want to know is, if __add__ performs an attribute look-up, is
that optimized in any way, after the IP is already in compiled code?
Af
IronPython doesn't have an interpreter loop and therefore has no POP / TOP /
etc... Instead what IronPython has is a method call Int32Ops.Add which looks
like:
public static object Add(Int32 x, Int32 y) {
long result = (long) x + y;
if (Int32.MinValue <= result
The end result of that is on a 32-bit machine IronPython runs in a 32-bit
process and on a 64-bit machine it runs in a 64-bit process.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike Driscoll
Sent: Friday, July 25, 2008 5:58 AM
To: python-list@python
>>
>> Oh, I know what you mean.
>> But that was exactly the reason for having a .DLLs folder, isn't it?
>> When you place an assembly into this folder, you avoid having to write
>> this boilerplate code, and simply import the assembly as you would
>> with a normal python module. At least, that´s ho
Currently IronPython doesn't support being hosted in WSH. It's something we've
discussed internally in the past but we've never had the cycles to make it work.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of misiek3d
Sent: Thursday, June 28, 2007 3:07 AM
Given a file foo.py:
def f():
You should get these results:
IronPython 1.0.60816 on .NET 2.0.50727.312
Copyright (c) Microsoft Corporation. All rights reserved.
>>> try:
... execfile('foo.py')
... except IndentationError, e:
... import sys
... x = sys.exc_info()
...
>>> print x[1].fi
Yes, IronPython generates IL which the JIT will then compile when the method is
invoked - so our parse/compile time is slower due to this. We've experimented
w/ a fully interpreted mode (which can be enabled with -X:FastEval) where we
walk the generated AST instead of compiling it, but that mod
Warnings is one of the features that didn't quite make it for v1.0. In general
w.r.t. non-ASCII characters you'll find IronPython to be more like Jython in
that all strings are Unicode strings. But other than that we do support
PEP-263 for the purpose of defining alternate file encodings.
We'
The first check is also off - it should if issubclass(type(Test), type):
otherwise you miss the metaclass case:
class foo(type): pass
class Test(object):
__metaclass__ = foo
obj = Test
if type(obj) == type: 'class obj'
else: 'not a class'
just on the off-chance you run into a metaclass :)
Hughes
Sent: Friday, April 28, 2006 1:00 PM
To: python-list@python.org
Subject: Re: Undocumented alternate form for %#f ?
Dino Viehland wrote:
> I'm assuming this is by-design, but it doesn't appear to be
> documented:
>
> >>> '%8.f' % (-1)
> '
I'm assuming this is by-design, but it doesn't appear to be documented:
>>> '%8.f' % (-1)
' -1'
>>> '%#8.f' % (-1)
' -1.'
The docs list the alternate forms, but there isn't one listed for f/F. It
would seem the alternate form for floating points is truncate & round the
floating poin
20 matches
Mail list logo
