I agree.
I could possibly understand removing the python 2 packages from a
distribution, but *removing them from a user's machine* is never excusable.
A policy like that is guaranteed to break something and, indeed, it did.
Good reasons to switch to Debian. :-)
-tk
On Mon, Apr 27, 2020 at 4:49
Cat22 writes:
> Here is the result of the bug I filed which has been closed by them as "wont
> fix":
> "Yes, we are removing all python2 packages from the distribution.
> If weewx maintainers haven’t noticed switch to python3 for eleven years, than
> you should complain with them."
Up to you
Here is the result of the bug I filed which has been closed by them as "wont
fix":
"Yes, we are removing all python2 packages from the distribution.
If weewx maintainers haven’t noticed switch to python3 for eleven years, than
you should complain with them."
so.
--
You received thi
On Sunday, 26 April 2020 02:34:59 UTC+10, Tom Keffer wrote:
>
> I tried Debian Buster in virtualbox and had the same issues appear
>>
>>
> I'm not following. Are you saying that a Buster upgrade removed pyserial
> and configobj?
>
That concerned me too, tried using serial under python2 on my des
On Saturday, April 25, 2020 at 9:34:59 AM UTC-7, Tom Keffer wrote:
>
> I tried Debian Buster in virtualbox and had the same issues appear
>>
>>
> I'm not following. Are you saying that a Buster upgrade removed pyserial
> and configobj?
>
No, I tried Buster by installing Debian in virtualbox as
>
> I tried Debian Buster in virtualbox and had the same issues appear
>
>
I'm not following. Are you saying that a Buster upgrade removed pyserial
and configobj?
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this grou
Here is the bug if anyone wants to follow it:
https://bugzilla.opensuse.org/show_bug.cgi?id=1170507
I tried Debian Buster in virtualbox and had the same issues appear
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from
That's what happened on my VM as well. Inexcusable that a seemingly
innocuous update would remove something without an upwardly compatible
replacement.
Or, switch to Debian? 😀
-tk
On Sat, Apr 25, 2020 at 9:16 AM Cat22 wrote:
>
>
> On Saturday, April 25, 2020 at 8:13:37 AM UTC-7, Cat22 wrote:
>
On Saturday, April 25, 2020 at 8:13:37 AM UTC-7, Cat22 wrote:
>
> I would prefer to stay on TW instead of reformatting to get back to 15.1
> I just filed a bug on TW about this.
> Everything has been working fine until a recent update (last couple of
> days actually)
>
> I found
>
python
On Saturday, April 25, 2020 at 8:13:37 AM UTC-7, Cat22 wrote:
>
> I would prefer to stay on TW instead of reformatting to get back to 15.1
> I just filed a bug on TW about this.
> Everything has been working fine until a recent update (last couple of
> days actually)
>
>
>
--
You received thi
I would prefer to stay on TW instead of reformatting to get back to 15.1
I just filed a bug on TW about this.
Everything has been working fine until a recent update (last couple of days
actually)
--
You received this message because you are subscribed to the Google Groups
"weewx-development"
1. Did you do "sudo zypper update" before trying?
2. Perhaps the difference is a Tumbleweed/Leap difference. Do you have to
be on Tumbleweed?
-tk
On Sat, Apr 25, 2020 at 7:29 AM Cat22 wrote:
> Neither of those work on my system
> e.g
>
> # zypper install python2-pyserial
> Loading repository da
Neither of those work on my system
e.g
# zypper install python2-pyserial
Loading repository data...
Reading installed packages...
'python2-pyserial' not found in package names. Trying capabilities.
No provider of 'python2-pyserial' found.
Resolving package dependencies...
Nothing to do.
# zypper
Slow down there...
I don't have Tumbleweed handy, but I do have Leap 15.1 on a VM. I tried
updating it and, yes, it did remove pyserial and configobj. Amazing.
However, they were easily reinstalled with
*sudo zypper install python2-pyserial*
*sudo zypper install python2-configobj*
Did you try t
Yes i386 is 32 bit, amd64 is 64bit. Which you use depends how you setup
your VM, or how you setup your VM will determine which ISO. Either will be
fine.
Gary
On Saturday, 25 April 2020 21:44:55 UTC+10, Cat22 wrote:
>
> Ok, my bad - i thought the amd64 said arm64 - I will restart the install
>
Ok, my bad - i thought the amd64 said arm64 - I will restart the install
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-development+unsubscr...@googl
Are you sure its not 32 bit? i386 sounds 32 bit to me but thats what i am
installing as we speak. I hope it turns out to be 64 bit
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving emails fro
Looks about right or it’s amd64 friend for 64bit.
Gary
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to weewx-development+unsubscr...@googlegroups.com.
To v
On Saturday, April 25, 2020 at 2:59:13 AM UTC-7, Cat22 wrote:
>
> I will try it via virtualbox and see how it goes. I'll post back here in a
> couple of days and let you know how i am doing.
> Thanks again for your help.
>
Is this correct?
https://cdimage.debian.org/debian-cd/current/i386/iso-c
I will try it via virtualbox and see how it goes. I'll post back here in a
couple of days and let you know how i am doing.
Thanks again for your help.
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop
Haven’t used any USB under virtualbox, do all my WeeWX development work on
Debian VMs under virtualbox but just use simulator, never with a live station.
Give 4b18 a go, only said to hold off to keep things simple, but then I
encountered tumbleweed.
Gary
--
You received this message because
I got into openSuse because we switched to it at work back around 200X and
I decided it would be a good thing to follow suit. We ran debian for our
development servers but we use suse for testing. I just cant make up my
mind about debian. maybe i'll install it in virtualbox and try it out. If I
SteelSeries will be fine, or if not an easy fix. I see b18 is the currently
available beta on the development downloads page, it’s about 24 days old though
most of the commits since b18 are fairly minor. I’d be tempted to give b18 a go.
Bit sneaky changing things like that, first time I have hea
On Saturday, April 25, 2020 at 2:06:15 AM UTC-7, gjr80 wrote:
>
> Interesting, https://software.opensuse.org/ says it does exist, though as
> I said I am not an openSUSE user. Might need an openSUSE user to help.
>
> WeeWX v4 is pretty stable. If you are (were) running a plain vanilla WeeWX
> i
Interesting, https://software.opensuse.org/ says it does exist, though as I
said I am not an openSUSE user. Might need an openSUSE user to help.
WeeWX v4 is pretty stable. If you are (were) running a plain vanilla WeeWX
install you should not have too many problems running the beta. The only iss
On Saturday, April 25, 2020 at 1:45:39 AM UTC-7, gjr80 wrote:
>
> OK so a missing python serial package is the issue. Not an openSUSE user
> but when I look at tumbleweed it shows a python-pyserial package and a
> python3-pyserial package. You can’t install python-pyserial?
>
> Gary
Yeh, I t
OK so a missing python serial package is the issue. Not an openSUSE user but
when I look at tumbleweed it shows a python-pyserial package and a
python3-pyserial package. You can’t install python-pyserial?
Gary
--
You received this message because you are subscribed to the Google Groups
"weewx
On Saturday, April 25, 2020 at 1:10:32 AM UTC-7, gjr80 wrote:
>
> Hi,
>
> > So, I am having issues running weewx because "Python 2.7 reached the end
> of its life on January 1st, 2020."
>
> I find this hard to believe. WeeWX v4, which is still in beta, (but will
> be released real soon now) w
I take it from that, that the software was crashing and stopping weewx when
run with that version of Python, where it would run correctly and produce
the correct results under all previous versions.\
Thanks for finding this out.
Susan
--
You received this message because you are subscribed to
Hi Susan,
the
https://github.com/hes19073/hesweewx/blob/master/bin/weewx/drivers/fousb.py
works
now error-free under python3.7.3
Hartmut
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving
Out of interest, what problem does this solve?
What are the symptoms you experienced that made you look for this?
Susan
--
You received this message because you are subscribed to the Google Groups
"weewx-development" group.
To unsubscribe from this group and stop receiving emails from it, send a
31 matches
Mail list logo
