Would be nice if we could tag issues in the issue tracker with for 2.7 or
something similar so people could know which issues were on the docket for
including in 2.7. This might help people who want to contribute to do so.
http://ironpython.codeplex.com/workitem/list/advanced
slide
On Thu, Jan
On Fri, Jan 21, 2011 at 6:58 AM, Slide slide.o@gmail.com wrote:
Would be nice if we could tag issues in the issue tracker with for 2.7 or
something similar so people could know which issues were on the docket for
including in 2.7. This might help people who want to contribute to do so.
On Fri, Jan 21, 2011 at 8:51 AM, Jeff Hardy jdha...@gmail.com wrote:
On Fri, Jan 21, 2011 at 6:58 AM, Slide slide.o@gmail.com wrote:
Would be nice if we could tag issues in the issue tracker with for 2.7
or
something similar so people could know which issues were on the docket
for
On Thu, Jan 20, 2011 at 10:08 PM, yngipy hernan yng...@gmail.com wrote:
I would like to get my hands wet with IronPython as well but it is not
straight forward where to start. I am no expert but I can hack around code
so I would need guidance where to start.
For instructions on getting the
On Fri, Jan 21, 2011 at 8:55 AM, Slide slide.o@gmail.com wrote:
This sounds great. Just need to make sure only certain people can mark
something as bug (to be) fixed in this release field so random people
don't just start marking things as going to be fixed in 2.7 :-)
You have to be a
Hi
Pulled src from github. The devel set up instructions
(http://ironpython.codeplex.com/wikipage?title=Respository%20Instructions)
and all the script magic already in place is just great as things
compile and run. Very cool.
However, need help figuring some things out, please:
1. Neither the
Daniel wrote:
Pulled src from github. The devel set up instructions
(http://ironpython.codeplex.com/wikipage?title=Respository%20Instructions)
and all the script magic already in place is just great as things compile and
run.
Very cool.
However, need help figuring some things out,
Thx on the IRONPYTHONPATH hint.
Regarding what blows up:
copy'n'paste Lib folder from cPython 2.7.1 into /Debug/.., followed by bdc
6 Warning(s)
0 Error(s)
Time Elapsed 00:00:37.34
C:\workipy
IronPython 2.7 Beta 1 DEBUG
Daniel wrote:
Thx on the IRONPYTHONPATH hint.
Regarding what blows up:
copy'n'paste Lib folder from cPython 2.7.1 into /Debug/.., followed by bdc
6 Warning(s)
0 Error(s)
Time Elapsed 00:00:37.34
C:\workipy
