Re: Building plans .....
Christopher Barker <[email protected]> Mon, 16 Mar 2020 08:57:02 -0700
| Newsgroups | gmane.comp.python.apple |
|---|---|
| Message-ID | <CALn7ch-fvA1g-57eHoy7wx9LTgzJCKP+JZ1NXXJvFkwPvRexsA@mail.gmail.com> |
--===============1722949614620209685== Content-Type: multipart/alternative; boundary="0000000000006ce5f005a0fadfa6" --0000000000006ce5f005a0fadfa6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, Mar 16, 2020 at 1:09 AM Georg Seifert <[email protected]> wrote: > > - A framework build is easier to integrate into applications that are > built using Xcode (just drop the framework into list of used frameworks) > > When would that come into play? If you are developing an application > that embeds the python interpreter? OR if you are using XCode as your IDE > for developing a Python App? > > > I=E2=80=99m using that in my app (written in ObjectiveC) to be able to ru= n python > scripts inside the app and to load plugins that are written in python but > don=E2=80=99t bring there own python interpreter. > Perfect -- and that's using Python more as a "library". So providing a Framework build is a good thing for these uses. Though I wonder if there's a need for a pre-built one with an installer --wouldn't folks using XCode be able to built it themselves? But either way, this isn't a use case for conda, or brew or .... Also, there's no reason that a "PythonFramework" couldn't be a separate package in conda -- you just wouldn't want to have all the other Python-y stuff depending on it. If you are embedding the interpreter, you are managing all the the dependencies anyway. Now someone just needs the time to do it :-( -CHB --=20 Christopher Barker, PhD Python Language Consulting - Teaching - Scientific Software Development - Desktop GUI and Web Development - wxPython, numpy, scipy, Cython --0000000000006ce5f005a0fadfa6 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr">On Mon, Mar 16, 2020 at 1:09 AM Georg Sei= fert <<a href=3D"mailto:[email protected]">[email protected]</a>&g= t; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_qu= ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20= 4);padding-left:1ex">> - A framework build is easier to integrate into a= pplications that are built using Xcode (just drop the framework into list o= f used frameworks)<br> > When would that come into play? If you are developing an application t= hat embeds the python interpreter? OR if you are using XCode as your IDE fo= r developing a Python App?<br> >=C2=A0 <br> I=E2=80=99m using that in my app (written in ObjectiveC) to be able to run = python scripts inside the app and to load plugins that are written in pytho= n but don=E2=80=99t bring there own python interpreter.<br></blockquote><di= v><br></div><div>Perfect -- and that's using Python more as a "lib= rary". So providing a Framework build is a good thing for these uses. = Though I wonder if there's a need for a pre-built one with an installer= --wouldn't folks using XCode be able to built it themselves? But eithe= r way, this isn't a use case for conda, or brew or ....</div><div><br><= /div><div>Also, there's no reason that a "PythonFramework" co= uldn't be a separate=C2=A0package in conda -- you just wouldn't wan= t to have all the other Python-y stuff depending on it. If you are=C2=A0emb= edding the interpreter, you are managing all the the dependencies anyway.</= div><div><br></div><div>Now someone just=C2=A0needs the time to do it :-(</= div></div><div><br></div><div>-CHB</div><div><br></div><div>--=C2=A0<br></d= iv><div dir=3D"ltr" class=3D"gmail_signature">Christopher Barker, PhD<br><b= r> Python Language Consulting<br>=C2=A0 - Teaching<br>=C2=A0 - Scientific S= oftware Development<br>=C2=A0 - Desktop GUI and Web Development<br>=C2=A0 -= wxPython, numpy, scipy, Cython<br></div></div> --0000000000006ce5f005a0fadfa6-- --===============1722949614620209685== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Pythonmac-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/pythonmac-sig unsubscribe: https://mail.python.org/mailman/options/Pythonmac-SIG --===============1722949614620209685==--