Re: [Ironpython-users] string/unicode

2016-09-17 Thread Tim Orling
As usual, I agree with you Pawel :) That said, I don't have a lot of "handcrafted tweaks for str/unicode aliasing", so it's easy for me to dismiss that negative. To me, your proposal sounds elegant, but I am open to consensus. --Tim On Sat, Sep 17, 2016 at 3:13 AM, Pawel Jasinski wrote: > hi,

Re: [Ironpython-users] numpy implementation [was Re: Community Meeting]

2016-07-13 Thread Tim Orling
Product Development Core Technology >>>> Memminger Str. 151 | 87439 Kempten | Germany >>>> Tel. +49-831-54031-979 | Fax +49-831-54031-50 >>>> >>>> E-Mail: m.scha...@codesys.com | Web: codesys.com >>>> <http://www.codesys.com> | CODESYS

Re: [Ironpython-users] Community Meeting

2016-07-11 Thread Tim Orling
On Mon, Jul 11, 2016 at 6:56 AM, Uncle Meat <3000@gmail.com> wrote: > Hi Haymo, > > I am very interested in having IPy support Numpy. I would be willing to > support the effort if you need some help. > > Numpy is a problem because of the amount of C extensions. The best hope, IMHO, is ironclad

Re: [Ironpython-users] Community Meeting

2016-07-11 Thread Tim Orling
On Mon, Jul 11, 2016 at 10:08 AM, Slide wrote: > See comments inline > > On Mon, Jul 11, 2016 at 1:45 AM Markus Schaber > wrote: > >> Hi, >> >> >> >> Just my personal thoughts on some of the topics: >> >> >> >> - IronRuby - What do we want to do here? >> >> >> >> To be honest, IronRuby is not my

Re: [Ironpython-users] IronPython Development Update

2016-07-08 Thread Tim Orling
> Thanks, > > Alex > > On Fri, Jul 8, 2016, 10:13 Tim Orling wrote: > >> Thank you for all the hard work in the past, Jeff. Glad to see Alex and >> Benedikt taking the helm. Great move :) >> >> On Fri, Jul 8, 2016 at 10:01 AM, Jeff Hardy wrote: >> &g

Re: [Ironpython-users] IronPython Development Update

2016-07-08 Thread Tim Orling
Thank you for all the hard work in the past, Jeff. Glad to see Alex and Benedikt taking the helm. Great move :) On Fri, Jul 8, 2016 at 10:01 AM, Jeff Hardy wrote: > It should be fairly obvious that IronPython has stagnated for a bit, and > that's mostly my fault for being a bottleneck. For many

Re: [Ironpython-users] Attracting new developers

2015-11-16 Thread Tim Orling
On Mon, Nov 16, 2015 at 1:08 PM, Tim Orling wrote: > > > On Mon, Nov 9, 2015 at 2:40 PM, Jeff Hardy wrote: > >> >> >> On Thu, Nov 5, 2015 at 9:41 PM, Tim Orling wrote: >> >>> >>> >>> On Nov 5, 2015, at 9:14 PM, Jeff Hardy wr

Re: [Ironpython-users] Attracting new developers

2015-11-16 Thread Tim Orling
On Mon, Nov 9, 2015 at 2:40 PM, Jeff Hardy wrote: > > > On Thu, Nov 5, 2015 at 9:41 PM, Tim Orling wrote: > >> >> >> On Nov 5, 2015, at 9:14 PM, Jeff Hardy wrote: >> >> On Thu, Nov 5, 2015 at 12:55 AM, Kuno Meyer wrote: >> >>> First, I

Re: [Ironpython-users] Attracting new developers

2015-11-05 Thread Tim Orling
> On Nov 5, 2015, at 9:14 PM, Jeff Hardy wrote: > >> On Thu, Nov 5, 2015 at 12:55 AM, Kuno Meyer wrote: >> First, I would start processing pending pull requests and react to bug >> reports on Github (merge / give feedback). A project that has virtually lost >> all active core developers and

Re: [Ironpython-users] Attracting new developers

2015-11-04 Thread Tim Orling
I have no suggestions, but completely agree with the sentiment. In particular, I would love to see some traction on PEP-380 , since that is the first thing that came up when I tried to use IP3. I had a look at the code