Sorry for the delay... One thing to note is you won't get any warnings like
PyLint provides, but it will let you interrogate the analysis. Here's the
basic code:
string code = "def f(): pass";
// create an interpreter instance and an analyzer for that
interpreter.
Could anyone link me on how to use PTVS's analyzer?
From: Dino Viehland [mailto:di...@microsoft.com]
Sent: Tuesday, September 30, 2014 8:12 PM
To: Joseph Mortensen; ironpython-users@python.org
Subject: RE: static analysis tool
Do you want to create your own static analysis rules or just use an ex
You should be able to do a clr.AddReference (r
clr.AddReferenceToFileAndPath) on the DLL and then import modules as
usual.
- Jeff
On Mon, Oct 13, 2014 at 11:15 PM, Chuck Dascalos wrote:
> I've figured out how to compile the library into a dll with the following
> command (running this from the r
Hi ironpython,
Here's your Daily Digest of new issues for project "IronPython".
In today's digest:ISSUES
1. [New comment] compile() does not recognize CO_FUTURE_PRINT_FUNCTION
2. [New issue] Installing a beta removes stable installation
3. [New comment] Installing a beta removes stable installat
