On 01/04/2010 08:59, Aravin wrote:
[snip...]
Also, if anyone is interested, I updated the compiler package found in
FePy to work with IronPython 2.6RC1.
I'm able to run pyFlakes on IronPython using it (also tried pySmell
and it works so far).
I'm fixing up errors as I encounter them. Is there any test cases that
I can run to make sure that the implementation works?
So if anyone wants to use the compiler package, let me know and I can
put it up on codeplex or something.
If you could make this publicly available somewhere that would be great.
There are quite a few projects that require the compiler package.
All the best,
Michael Foord
Is there a way to convert the compiler.ast to _ast?
Thanks,
Aravin
On Thu, Mar 25, 2010 at 9:52 PM, Michael Foord
<fuzzy...@voidspace.org.uk <mailto:fuzzy...@voidspace.org.uk>> wrote:
On 25/03/2010 13:44, Jeff Hardy wrote:
On Thu, Mar 25, 2010 at 5:10 AM, Michael Foord
<fuzzy...@voidspace.org.uk <mailto:fuzzy...@voidspace.org.uk>>
wrote:
They almost certainly use the compiler / ast modules that
aren't available
for IronPython. You can ship CPython as part of your
application though,
without needing it to be installed.
http://bitbucket.org/jdhardy/_ast/
There's one compiler error under 2.6 (a function is
missing/renamed);
I just haven't had a chance to figure it out.
That said, if pyflakes/pysmell use 'compiler' instead of
'ast', you're
probably hooped. Compiler is unlikely to ever be supported.
I think FePy used to have support for the compiler module, but I'm
having a hard time figuring out where that was implemented.
All the best,
Michael
- Jeff
_______________________________________________
Users mailing list
Users@lists.ironpython.com <mailto:Users@lists.ironpython.com>
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
READ CAREFULLY. By accepting and reading this email you agree, on
behalf of your employer, to release me from all obligations and
waivers arising from any and all NON-NEGOTIATED agreements,
licenses, terms-of-service, shrinkwrap, clickwrap, browsewrap,
confidentiality, non-disclosure, non-compete and acceptable use
policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in
perpetuity, without prejudice to my ongoing rights and privileges.
You further represent that you have the authority to release me
from any BOGUS AGREEMENTS on behalf of your employer.
_______________________________________________
Users mailing list
Users@lists.ironpython.com <mailto:Users@lists.ironpython.com>
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
http://www.ironpythoninaction.com/
http://www.voidspace.org.uk/blog
READ CAREFULLY. By accepting and reading this email you agree, on behalf of
your employer, to release me from all obligations and waivers arising from any
and all NON-NEGOTIATED agreements, licenses, terms-of-service, shrinkwrap,
clickwrap, browsewrap, confidentiality, non-disclosure, non-compete and
acceptable use policies (”BOGUS AGREEMENTS”) that I have entered into with your
employer, its partners, licensors, agents and assigns, in perpetuity, without
prejudice to my ongoing rights and privileges. You further represent that you
have the authority to release me from any BOGUS AGREEMENTS on behalf of your
employer.
_______________________________________________
Users mailing list
Users@lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
