4
I Use This!
Moderate Activity

Commits : Listings

Analyzed about 18 hours ago. based on code collected about 20 hours ago.
Jul 24, 2025 — Jul 24, 2026
Commit Message Contributor Files Modified Lines Added Lines Removed Code Location Date
merge from patstew-master More... almost 13 years ago
- Ensure python threads are always initialized, even if the main interpreter hasn't initialized them, otherwise attempting to dereference objects in finalizers called by the concurrent GC will fail. - Dispose of PyObject instances after use in CreateSubType rather than wait for the GC - Don't try and dereference derived class instances after python has shutdown if called from the GC More... almost 13 years ago
creating instances of classes that are managed types sub-classed in python from managed code now works More... almost 13 years ago
managed types can now be subclassed in python and override virtual methods More... almost 13 years ago
Add missing ) so sample code in README works More... almost 13 years ago
Update README.md More... about 13 years ago
Fix readme formatting. More... about 13 years ago
Create README.md More... about 13 years ago
Use the c# dynamic functionality for python objects. This means that python functions can be called directly, members can be accessed as normal (a.b) and mathematical operations work, and run in python (a = b*c). More... about 13 years ago
Add convenience functions to new Py class. Supports "using (Py.GIL()) {}" blocks to setup the python interpreter and take/release the GIL, and Py.kw("key1", value1, "key2", value2, ...) to add keyword arguments. More... about 13 years ago
Add more of the PyNumber API to support mathematical operations. More... about 13 years ago
Update c# project More... about 13 years ago
Convert IEnumerables to python lists. More... about 13 years ago
Fix crash because Python 3 C API does not have PyNumber_Int More... about 13 years ago
add Python 3 support More... about 13 years ago
# BUGFIX: Accommodate new output path (x86 vs. x64) # More... over 13 years ago
# Move DEBUG_PRINT to the Properties->Build page of the DebugWin Configuration. # More... over 13 years ago
# FIXED: .sln and .csproj file configurations x86/x64 Mono/Win Debug/Release all reflected throughout # # Added Conditional Reference <Choose> <When> elements to Python.Runtime.csproj => building for Mono on Windows # # Added Required reference assemblies => building for Mono on Windows # More... over 13 years ago
Of course, for the previous to work, you'll be needing the project files to go with... But we don't need another copy of that signing key laying around. More... over 13 years ago
# Solution Configurations for each VS and MD - We'll release x86 and x64 binaries separately. # MonoDevelop will now share the solution and project files with Visual Studio quite nicely. In fact, MD refers to .mds files as MD 1.x Solution Files. Separate configs supports different character widths on each OS platform. Platform specific settings are due, in part, to the introduction of DllExport's requirement (which actually only applies on Windows) Hmmm... Perhaps the Linux guy will want to revert to Any CPU # More... over 13 years ago
# NUnit issues begin to resolve themselves (amazing, really) since MD supports NuGet now, just grab NUnit and add it to /packages/. Honestly, though, I did have to trick NuGet into giving me the UnmanagedExport update. More... over 13 years ago
# Visual Studio 2010 .NET 4.0 (with a little ReSharper thrown in) # # The new C# clrmodule depends on RGiesecke.DllExport in new pythonnet/packages directory which was import via NuGet # # The signing key finally landed in the correct directory # # Not sure why the console/Console.csproj referenced Python.Test # # Python.Runtime Assembly version bumped to 4.0.0.1 # # Tool and Framework versions all bumped for .NET 4.0 # # [Obsolete?] buildclrmodule.bat got a tiny note after cli research on clrmodule.il # More... over 13 years ago
NOTE: All this maintenance led to the soon-to-be-committed DllExport enable module: # Cleanup after much ildasm and research: .fixup, .vtentry, etc. are all handled by the build system since late .NET 2.0. So there's no need to import the platform any longer. There's no fear of conflict with Linux - Mono needs a completely different mechanism (clr.so) to get the "Late Binding" ball rolling. # # There is a big chunk of notes taken regarding my findings # More... over 13 years ago
# Add Signing Key # More... over 13 years ago
Added new usage on "Overloads" More... over 13 years ago
Update links which were broken since SF upgrade More... over 13 years ago
# Add Signing Key # More... over 13 years ago
# VS 2008 => 2010 project files (remain compatible with 2008) # More... over 13 years ago
# Update notes on "failed" tests " More... over 13 years ago
# Build using %windir%\Microsoft.NET\Framework\v4.0.30319\ilasm # # Remove duplicate script (perhaps intended to build alternate clr versions???) # More... over 13 years ago