This is an automated email letting you know that sources
have recently been pushed out. You can download these newer
sources directly from
http://ironpython.codeplex.com/SourceControl/changeset/view/59464.
MODIFIED SOURCES
$/IronPython/IronPython_Main/Src/IronPython/Modules/Builtin.cs
On Tue, Sep 22, 2009 at 09:56:58PM +0300, Markus T�rnqvist wrote:
On Tue, Sep 22, 2009 at 09:43:50AM -0600, Jeff Hardy wrote:
I'd like to help more, but I'm a bit overwhelmed at the moment - sorry.
[...]
Anyway, I'll tell you which way it goes, don't worry about that :D
I upgraded to IronPython
Yup. NWSGI beta 2 was built against older version. Either rebuild or use
assembly rebinding
http://aspadvice.com/blogs/ssmith/archive/2006/11/15/AssemblyBinding-in-Web-Config-and-XMLNS.aspx
On Fri, Sep 25, 2009 at 6:14 PM, Markus Törnqvist m...@nysv.org wrote:
On Tue, Sep 22, 2009 at 09:56:58PM
On Fri, Sep 25, 2009 at 06:22:24PM +0200, Dody Gunawinata wrote:
Yup. NWSGI beta 2 was built against older version. Either rebuild or use
assembly rebinding
http://aspadvice.com/blogs/ssmith/archive/2006/11/15/AssemblyBinding-in-Web-Config-and-XMLNS.aspx
Thanks, man, for the quick reply :D
Hi Vernon,
I presume you're talking django-mssql
(http://code.google.com/p/django-mssql/)? I always wondered why it had
its own database layer.
I don't think adodbapi is the best place to have django (or any other
ORM) specific stuff. django-mssql shoul talk to your module, and then
it should (in
On Fri, Sep 25, 2009 at 12:22 PM, Markus Törnqvist m...@nysv.org wrote:
I configured for 1.0.0.0 as Properties of Microsoft.Scripting.DLL says and
2.6.10920.0 for IronPython.dll.
AND IT WORKS! :)
Good to know! (I haven't had time to respin NWSGI for RC1 yet -
hopefully this weekend). Once
On Fri, Sep 25, 2009 at 12:35:08PM -0600, Jeff Hardy wrote:
On Fri, Sep 25, 2009 at 12:22 PM, Markus Törnqvist m...@nysv.org wrote:
I configured for 1.0.0.0 as Properties of Microsoft.Scripting.DLL says and
2.6.10920.0 for IronPython.dll.
AND IT WORKS! :)
Good to know! (I haven't had time to
On Fri, Sep 25, 2009 at 1:01 PM, Markus Törnqvist m...@nysv.org wrote:
I haven't debugged this too much, yet, but I'm not sure what to make of it.
I certainly never had a settings.SESSION_ENGINE, and when I run CPython
and manage.py runserver elsewhere with tracing in the sources, I see it
As we work towards our IronPython 2.0.3 bugfix release, Dino and I would like
to get a feel for which bugs left unresolved in 2.0.2 are most important for us
to fix in the next release. Please let us know ASAP if there's an issue you'd
like to see fixed in IronPython 2.0.3. Thanks!
