Hi Dino,
On Thu, Sep 1, 2011 at 7:07 PM, Dino Viehland wrote:
> Ahh yeah, I think I had some weird 1.5 build on my laptop where I tried it.
> Guess it's time to upgrade.
Same in 1.6, but I fixed it in "default" today.
Armin
___
Ironpython-users mailin
Antonio wrote:
> it seems to work fine with pypy 1.6. Note that str() is called twice for each
> line, so we get 1, 3, 5, 7..., but this happens only on cpython.
Ahh yeah, I think I had some weird 1.5 build on my laptop where I tried it.
Guess it's time to upgrade.
_
Great, thanks for the hint. If I manage to produce something, I'll try to
publish it as a reusable tool.
Igor
On Thu, Sep 1, 2011 at 2:06 PM, Michael Foord wrote:
> On 01/09/2011 10:04, Igor Brejc wrote:
>
> Hi,
>
> I plan to write a wrapper API in C# that will be used by IronPython
> scripts
Hi,
On Thu, Sep 1, 2011 at 10:57 AM, Armin Rigo wrote:
> It works as expected on CPython 2.7. Is it a bug? :-)
Fixed in 414bb2d98b0c.
Armin
___
Ironpython-users mailing list
Ironpython-users@python.org
http://mail.python.org/mailman/listinfo/ironpyt
On 01/09/11 10:57, Armin Rigo wrote:
Hi,
On Thu, Sep 1, 2011 at 9:58 AM, Antonio Cuni wrote:
it seems to work fine with pypy 1.6. Note that str() is called twice for
each line, so we get 1, 3, 5, 7..., but this happens only on cpython.
...but this happens only on PyPy, you mean. It works a
Hi,
On Thu, Sep 1, 2011 at 9:58 AM, Antonio Cuni wrote:
> it seems to work fine with pypy 1.6. Note that str() is called twice for
> each line, so we get 1, 3, 5, 7..., but this happens only on cpython.
...but this happens only on PyPy, you mean. It works as expected on
CPython 2.7. Is it a b
On 01/09/11 05:28, Dino Viehland wrote:
This came up on an internal discussion, I thought it was fun, especially given
that we all behave differently:
Paste this into the REPL:
[cut]
it seems to work fine with pypy 1.6. Note that str() is called twice for each
line, so we get 1, 3, 5, 7...,
On 01/09/2011 10:04, Igor Brejc wrote:
Hi,
I plan to write a wrapper API in C# that will be used by IronPython
scripts. The API will adhere to Python's coding & design style etc.
My question: what would be the best approach for generating code
documentation in HTML that would look & feel lik
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [Status update] xml.sax.make_parser() exception
2. [New comment] Implement pyexpat module
--
ISSUES
1. [Status update] xml.sax.make_parser()
Hi,
I plan to write a wrapper API in C# that will be used by IronPython scripts.
The API will adhere to Python's coding & design style etc.
My question: what would be the best approach for generating code
documentation in HTML that would look & feel like it's for native Python
API? Sandcastle see
10 matches
Mail list logo
