Mailman 3 June 2019 - Python.NET

FW: [pythonnet/pythonnet] Require at least .NET 4.7.1 (#897)
by Victor “LOST” Milovanov 26 Jun '19

26 Jun '19

FYI From: Benedikt Reinartz Sent: Tuesday, June 25, 2019 11:20 PM To: pythonnet/pythonnet Cc: Subscribed Subject: [pythonnet/pythonnet] Require at least .NET 4.7.1 (#897) For future .NET Standard compatibility and access to some nice simplifications in getting the platform (https://docs.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.… and https://docs.microsoft.com/en-us/dotnet/api/system.runtime.interopservices.… instead of getting the respective information via Python) it would be good to raise our .NET requirement to 4.7.1 or 4.7.2. Would this pose serious problems for anyone? Upgrading the runtime should usually always be possible and we already require at least 4.0, I think in some cases even 4.5. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

1 0

Minutes from meeting Tuesday June 25
by Mark Visser 25 Jun '19

25 Jun '19

Present: denis.akhiyarov(a)gmail.com amos_402(a)msn.com jared(a)quantconnect.com alex(a)quantconnect.com lostfreeman(a)gmail.com filmor(a)gmail.com markv(a)unity3d.com (sorry if I missed anyone) - Denis (denis.akhiyarov(a)gmail.com) stepped down from project ownership - Benedict (filmor(a)gmail.com) is most senior python net developer so will take over project ownership - Mark (markv(a)unity3d.com) offered to take care of administrative stuff (meetings, etc) and will schedule next meeting 2 hours earlier on Tuesday July 2 - should pythonnet join the .NET Foundation? AppVeyor account might make it worth it - vote next meeting - development resources for the future? - performance improvements - missing features - maintenance - merging QuantConnect fork into main repo? Benedict will review QC's fork with Jared (jared(a)quantconnect.com) and merge or suggest changes - Benedict will trim admin rights to only active committers - Please use issues for proposed work to be done and use "Epic" tag. suggested: - .NET core work - Python 3.8 work - other refactoring or features - Victor ( lostfreeman(a)gmail.com) will make PRs for key parts from his fork - Benedict suggested that we should move as much work as possible into the main repo - concern from QuantConnect that their velocity might be impacted - mitigated by keeping work flowing from QC fork to pythonnet/pythonnet?

1 0

Python for .NET Development Doodle Google Hangouts Meeting Invite
by Denis Akhiyarov 24 Jun '19

24 Jun '19

Please fill out this form with time slots available to you: https://doodle.com/poll/9asah3hczm3vvhtp All times are displayed at least for me in America/Chicago Central US Time Zone, but it may display for you in your time zone. Please verify it before making your selections. We have about 10 people who responded previously. A Google Hangout meeting invite is going to be sent out in 4-5 days to those who complete this form. A separate form with questionnaire to complete is going to be sent out few days before this online meeting. Thanks, Denis

1 1

pythonnet development
by Denis Akhiyarov 15 Jun '19

15 Jun '19

I would like to step down from pythonnet development, this mailing list, and helping out on stackoverflow. If someone is interested in moderating this mailing list, please reach out to me. Thanks, Denis

7 9

Re: [Python.NET] PythonDotNet Digest, Vol 175, Issue 3
by Jared Broad 15 Jun '19

15 Jun '19

QuantConnect's questions for the community: - Who are you? Where are you based? Are you an individual or a company? - Out of 10, 1 being a low priority, 10 being critical to survival, where would you place PythonNet's priority in your organization? - Are you winning to sponsor the project to hire a full-time developer? (e.g. 10 companies, $500 ea). - Order the following priorities for PythonNet future from first is most important: *Speed, Stability, Python Version Support, Supported Features (e.g. named args), Documentation, Promotion/Website, **Support for **Community Questions* ᐧ On Tue, Jun 11, 2019 at 8:31 AM <pythondotnet-request(a)python.org> wrote: > Send PythonDotNet mailing list submissions to > pythondotnet(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/pythondotnet > or, via email, send a message with subject or body 'help' to > pythondotnet-request(a)python.org > > You can reach the person managing the list at > pythondotnet-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of PythonDotNet digest..." > > > Today's Topics: > > 1. Re: pythonnet development (Denis Akhiyarov) > 2. Re: pythonnet development (David Lassonde) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 10 Jun 2019 22:10:57 -0500 > From: Denis Akhiyarov <denis.akhiyarov(a)gmail.com> > To: "A list for users and developers of Python for .NET" > <pythondotnet(a)python.org> > Cc: Benedikt Reinartz <filmor(a)gmail.com> > Subject: Re: [Python.NET] pythonnet development > Message-ID: > < > CALxxJLRxG0SV0iQxf--KGoyw3yVAhM-enN8HfcX5-eKx-fTnNw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > We are planning to have a conversation about the future of the project and > most important questions with developers who responded. Please reply if you > are interested in joining this chat. > > On Sat, Jun 8, 2019, 12:00 AM Victor ?LOST? Milovanov < > lostfreeman(a)gmail.com> > wrote: > > > What do you mean by ?reach out in GitHub repo?? Is there an issue for > this > > we could comment on? > > > > > > > > I could consider stepping up, but > > > > > > > > 1. I am relatively new to the project, and > > 2. My interest only lies in ensuring Python.NET continues to work from > > .NET. I?d be very sloppy responding to anything related to reverse > > embedding. > > > > So it is only possible, if there is someone else with more experience > with > > the project. > > > > > > > > At this moment I don?t even fully understand its architecture (which > could > > be fixed by a Skype session, or, much better, 1-2 in-person meetings). > > > > > > > > Regards, > > > > Victor > > > > > > > > *From: *Denis Akhiyarov <denis.akhiyarov(a)gmail.com> > > *Sent: *Friday, June 7, 2019 3:47 PM > > *To: *A list for users and developers of Python for .NET > > <pythondotnet(a)python.org> > > *Cc: *Benedikt Reinartz <filmor(a)gmail.com> > > *Subject: *Re: [Python.NET] pythonnet development > > > > > > > > Hi Victor, > > > > > > > > Are you interested in getting involved? Please reach out in GitHub repo. > > If anyone is really serious about this commitment, please send me a > private > > message. I received some private interest as well as a Twitter thread: > > > > > > > > https://mobile.twitter.com/denfromufa/status/1137032838287699969 > > > > > > > > On Fri, Jun 7, 2019, 12:45 PM Victor ?LOST? Milovanov < > > lostfreeman(a)gmail.com> wrote: > > > > Hi Denis, > > > > > > > > Who are the current maintainers of Python.NET repo? > > > > > > > > Regards, > > > > Victor > > > > > > > > *From: *Denis Akhiyarov <denis.akhiyarov(a)gmail.com> > > *Sent: *Friday, June 7, 2019 6:31 AM > > *To: *A list for users and developers of Python for .NET > > <pythondotnet(a)python.org> > > *Cc: *Benedikt Reinartz <filmor(a)gmail.com> > > *Subject: *[Python.NET] pythonnet development > > > > > > > > I would like to step down from pythonnet development, this mailing list, > > and helping out on stackoverflow. > > > > > > > > If someone is interested in moderating this mailing list, please reach > out > > to me. > > > > > > > > Thanks, > > > > Denis > > > > > > > > _________________________________________________ > > Python.NET mailing list - PythonDotNet(a)python.org > > https://mail.python.org/mailman/listinfo/pythondotnet > > > > > > _________________________________________________ > > Python.NET mailing list - PythonDotNet(a)python.org > > https://mail.python.org/mailman/listinfo/pythondotnet > > >

7 6

Re: [Python.NET] pythonnet development
by Li Amos 15 Jun '19

15 Jun '19

Interesting for it, count me in.

1 0

Retiring Python 2.7
by Victor “LOST” Milovanov 14 Jun '19

14 Jun '19

Python 2.7 end of life is set to Jan 1st 2020, which is just a bit over 6 months now. https://pythonclock.org/ Major packages, like numpy are planning to drop support too. I think we should have some kind of plan to retire Python 2.x support in Python.NET. First of all, it would be good to know if there are anyone actually using Python 2.7 via Python.NET, and what is your plan going forward past EoL. Regards, Victor Milovanov

7 9