Hi.
Someone has fixed this:
http://ironpython.codeplex.com/workitem/28863
at some point between 2.6.x and 2.7.
How do I go and close my own bugs?
Daniel.
___
Users mailing list
Users@lists.ironpython.com
Re: IRONPYTHONPATH
It looks like the magic is already in place in dev.bat to set
[IRON]PYTHONPATH to the right path. However, the setting is
conditional on If DEFINED THISISSNAP
I am not a stupid fella, but i had to resort to bugging you and asking
about the modules set up. I am sure there are /
A example / proposed patch attached to the bug.
Short note on sending in patches. The best way to propose patches is to
create your own fork of the IronPython
sourceshttps://github.com/IronLanguages/mainon github (docs:
http://help.github.com/forking/). After making your change and testing
Daniel wrote:
Re: IRONPYTHONPATH
It looks like the magic is already in place in dev.bat to set [IRON]PYTHONPATH
to the right path. However, the setting is conditional on If DEFINED
THISISSNAP
I am not a stupid fella, but i had to resort to bugging you and asking about
the
modules set
On Sun, Jan 23, 2011 at 1:32 AM, Daniel D. dvdotse...@gmail.com wrote:
Hi.
http://ironpython.codeplex.com/workitem/28235
A example / proposed patch attached to the bug.
Patch applied as 0cd.
I think matching the CPython behaviour here is pretty critical,
especially since it is also a
I committed the patch using '.' as the current directory; if anyone
(Dino?) needs the fully resolved path ...
The . (rather ) in cPy is a neat trick. It's added only in
interactive (console, -c) cases and allows you to change the CWD
to the dir you want and have your custom modules picked up
Hi.
Building and tweaking in VS 2010 Express is quite a tolerable
experience (once a sensible coloring theme is applied
http://studiostyl.es/schemes/contentisking).
I see this on
http://ironpython.codeplex.com/wikipage?title=Respository%20Instructions
:
Build the DLR COM library as
How about distributing precompiled dll's for the testing pieces that are
absent
on VS 2010 Express (SHarpDevel) installs?
I think this would be a good idea. If we ever plan on getting the unit tests
running on the continuous integration server, it's unlikely to have a full
Visual Studio
On Sun, Jan 23, 2011 at 12:36 PM, Daniel D. dvdotse...@gmail.com wrote:
I committed the patch using '.' as the current directory; if anyone
(Dino?) needs the fully resolved path ...
The . (rather ) in cPy is a neat trick. It's added only in
interactive (console, -c) cases and allows you to
On Sun, Jan 23, 2011 at 2:05 PM, Richard Nienaber rjniena...@gmail.com wrote:
How about distributing precompiled dll's for the testing pieces that are
absent
on VS 2010 Express (SHarpDevel) installs?
I think this would be a good idea. If we ever plan on getting the unit tests
running on the
On 23/01/2011 21:14, Jeff Hardy wrote:
On Sun, Jan 23, 2011 at 12:36 PM, Daniel D.dvdotse...@gmail.com wrote:
I committed the patch using '.' as the current directory; if anyone
(Dino?) needs the fully resolved path ...
The . (rather ) in cPy is a neat trick. It's added only in
interactive
I was just commenting on . vs. fully resolved I just don't see a
point for fully resolved CWD ref from the start in console mode,
when . is present.
Re cPy's use of instead of .
I know it's pervasive on cPy side, and I used that form for .listdir()
(which, incidentally, works with on os. and
Jeff wrote:
For a nice easy fix to start with, take a look at
http://ironpython.codeplex.com/workitem/29928. You can either attach a
patch to the issue, or (preferably) create a fork on GitHub and send us a pull
request.
Here's some other bugs which look like they might be good to start on.
13 matches
Mail list logo
