That required sudo apt install python3-pip python3-setuptools python3.9-venv
and that worked, phew! On Tue, Jan 12, 2021 at 2:09 PM Forrest Curo <[email protected]> wrote: > Okay, re that pesky virtual environment. Upgrading my ubuntu distribution > made for a clearer error message: > > "The virtual environment was not created successfully because ensurepip is > not > available. On Debian/Ubuntu systems, you need to install the python3-venv > package using the following command. > > apt-get install python3-venv > > ..." > > Onward, thanks. > > > On Sat, Jan 9, 2021 at 8:12 AM Iain Duncan <[email protected]> > wrote: > >> That sounds very cool, I look forward to checking it out. I was curious >> about the scheduler, as my experience (limited) has been that Python is >> quite frustrating for soft-real time. But the other stuff sounds awesome, >> and like this could be a great "gateway drug" to CM with other languages. >> :-) >> >> In obliquely related news, I'm very close to having my interaction with >> the Max scheduler code doing what I want nicely, so being able to run S7 CM >> in Max is getting close! >> >> iain >> >> >> On Fri, Jan 8, 2021 at 5:36 PM Taube, Heinrich K <[email protected]> >> wrote: >> >>> > out of curiosity, which features of Common Music are not in there? >>> >>> the biggest missing piece is no connection to sndlib. But sndlib has its >>> XEN bindings to forth and ruby and Python has Cython for implementing >>> things at the C level so i expect that a binding could be made to python as >>> well. musx is lacking MusicXml input, but Grace didnt have that either >>> after fomus stopped being supported. I think maybe the right way to do >>> musicxml input/ouput would be use something like DSGenerate to >>> automatically generate Python musicxml classes directly from its schema. >>> musx has no realtime scheduler. Python has threads so maybe it could be >>> done (or they could be implemented in Cython, similar to how I did it Grace >>> using Juce threads). xmus patterns are implemented using python generators >>> (functions), so dont have all the expressibility as the patterns in CM. But >>> its totally possible to just port CMs pattern classes, I just havent done >>> it yet. The generators are simpler and work well for most patterns. musx >>> actually has some features not in cm , right now it has basic music theory >>> objects Pitch and Interval and there are some other theory things like set >>> tools and score/part representations I already have but havent put them in >>> yet until music xml support is there. grace had a plotter, but musx doesnt >>> need one since python's matplotlib package can be used and is much more >>> powerful. i think those are pretty much the differences - musx is able to >>> run all the grace demo examples so the systems are pretty close. >>> >>> —Rick >>> >>> _______________________________________________ >> Cmdist mailing list >> [email protected] >> https://cm-mail.stanford.edu/mailman/listinfo/cmdist >> >
_______________________________________________ Cmdist mailing list [email protected] https://cm-mail.stanford.edu/mailman/listinfo/cmdist
