<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I use python on a daily basis for scientific computing (PyTorch, Matplotlib, Numpy, Scipy, scikits-learn, etc.). Python is great for doing quick projects, but certain design features of the language make it less ideal for large projects (e.g. whitespace, weak typing, speed, etc.). Swift shares many of the nice qualities Python has but without some of the warts.<div class=""><br class=""></div><div class="">To answer your question, I think anyone who needs to integrate their algorithm into larger projects and/or on hardware care about moving away from Python. <br class=""><div class=""><br class=""></div><div class="">I think trying to include Python libraries makes sense. Julia did the same thing, which allowed them to grow their user base very quickly (e.g. being able to use Matplotlib in Julia was a huge win). I believe the way Julia imports Python libraries is via its extremely powerful (and complex) macro system.</div><div class=""><br class=""></div><div class="">While using Python via Swift is a great way to use already written libraries, my preference would be to eventually write everything in Swift (trying to debug across languages can be painful). I did (a while ago) write a Tensor library for Swift, but ran into some issues when trying to make it run both on the CPU and GPU. A new approach I’m considering is to instead wrap a pre-existing C library.</div><div class=""><br class=""></div><div class="">My two cents, as the question of users was brought up.</div><div class=""><br class=""></div><div class="">A</div><div class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 4, 2017, at 12:15 PM, Tino Heth via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><br class=""><blockquote type="cite" class=""><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">This is a bridge to allow easy access to the vast number of libraries that currently exist in those dynamic language domains, and to ease the transition of the multitudes of those programmers into Swift.</span></div></blockquote></div><br class=""><div class="">I’ve read several posts that gave me the impression that Python has a huge user base of people who are tired of using that language (the cited statement is just an arbitrary pick)… but is that actually true?</div><div class="">Afaik, Python never became as common as Java, C# or C++, and it never had much support from big companies — people decided to use Python not because it’s some sort of standard, but because they liked it and found it to be a language that’s easy to learn.</div><div class=""><br class=""></div><div class="">So the whole story of „let’s make it easier for those poor Python guys to switch to a real language“ sounds very much like hubris to me.</div><div class="">Of course, that statement is an exaggeration, but still:</div><div class="">Did anyone ever ask the Python-community who actually wants to switch to Swift? I don’t think there would be enough positive feedback to take it as a justification for the proposed changes.</div><div class=""><br class=""></div></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></div></div></body></html>