Dino Viehland wrote:
Michael wrote:
I've had to use these several times and they are also used in Ironclad.
Documentation, *especially* of the changes, would be very useful.
We're going to spend some time in the next couple months on writing and
packaging up some useful documentation.
Michael wrote:
> I've had to use these several times and they are also used in Ironclad.
> Documentation, *especially* of the changes, would be very useful.
We're going to spend some time in the next couple months on writing and
packaging up some useful documentation. This is definitely one are
> There's a couple of places in NWSGI where I need a CodeContext, so
> I've just been creating an empty one like so and using it (and it's
> worked so far):
> new CodeContext(new Scope(),
> HostingHelpers.GetLanguageContext(engine))
>
> Now, in 2.6 RC I need a PythonDictionary instead of a sco
Jeff Hardy wrote:
There's a couple of places in NWSGI where I need a CodeContext, so
I've just been creating an empty one like so and using it (and it's
worked so far):
new CodeContext(new Scope(), HostingHelpers.GetLanguageContext(engine))
Now, in 2.6 RC I need a PythonDictionary instead of
There's a couple of places in NWSGI where I need a CodeContext, so
I've just been creating an empty one like so and using it (and it's
worked so far):
new CodeContext(new Scope(), HostingHelpers.GetLanguageContext(engine))
Now, in 2.6 RC I need a PythonDictionary instead of a scope (easy
enoug
