Hi Stuart,
Never knew any of the mailing lists took attachments. I hope no one
starts posting videos.
Fascinating about the packages. Maybe it wasn't all my fault. That would
be a first time! And thanks for the reminder of how to save the names of
all the ports.
Yes, I noticed that I was having problems with Python as well. Was
writing a bit of code to generate DTMF tones for ham radio repeater
controls, plus so I can get dumb phones to listen to long sequences from a
tiny pocket computer, where I can append calling card number and pin to
call US & international long distance for a penny a minute.
Telus has a new $10 a month "wireless home phone", no charge for the
device, and free calls across Canada, but they are hoping to make up for
it by getting you to sign up for US and international service extra cost.
Also, they think they have modems, and hence data, blocked in that
service. I think I can program around that, even if a bit slow.
It's a neat device. You can take it camping with you, and not have to
forward your base home or office number. Maybe I can make a poor man's
cell phone out of it, just for fun.
I'll let you know how I make out with the packages.
Austin
On Sun, 2 Aug 2020, Stuart Henderson wrote:
> On 2020/08/01 17:38, Austin Hook wrote:
> >
> > Hi Stuart,
> > Here's the full typescript attached. The list itself chops off
> > attachments I think, but I am sure any of us can delete my email, or even
> > save after deleting the attachment, as I often do within alpine with long
> > videos of funny cats, or political polemics that my relatives can't resist
> > sending.
>
> Ports@ allows attachments, they are used often.
>
> One problem is that the update path from old Python 3.x to newer 3.x was
> broken (I fixed it between 6.6 and 6.7), this gets in the way of merging
> gettext from the old to new names - no registered update path so it tries
> to keep the old Python package, but the old package depends on old gettext
> which conflicts with the newer one.
>
> Either jumping to 6.7 or removing/reinstalling all packages (as per my
> previous mail) would fix that problem.
>
> There maybe other problems but it's hard to identify them after the
> noise from the first one.
>
No comments:
Post a Comment