Posts by fairbird

    For example this code using

    Code
    .format(xx)

    for python 3.15.4 but with python 3.15.5 need to change to

    Code
    f"{pathLoc}bqts"


    old code

    Code
    if os.path.exists("{}bqts".format(pathLoc)):
    
    with open("{}bqts".format(pathLoc), "r") as f:
        refs = f.readlines()

    after change .. It is more better and smoothly +added (encoding)

    Code
    bqts_path = f"{pathLoc}bqts"
    if not os.path.exists(bqts_path):
    
    with open(bqts_path, "r", encoding="utf-8") as f:
        refs = f.readlines()


    also change Loop Structure and Event Processing


    old

    Code
    nl = len(refs)
    for i in range(nl):
        ref = refs[i]


    new

    Code
    for ref in refs:
        ref = ref.strip()
        if not ref:
            continue

    Reason: Direct iteration is more Pythonic and readable. Stripping whitespace and skipping empty lines prevents processing invalid references, improving robustness.also use (int)old

    Code
    n = config.plugins.xtraEvent.searchNUMBER.value
    for i in range(int(n)):
        title = events[i][4]
        description = events[i][6]


    new

    Code
    n = int(config.plugins.xtraEvent.searchNUMBER.value)
    for i in range(min(n, len(events))):
        title = events[i][4] or ""  # Default to empty string
        description = events[i][6] or ""  # Default to empty string


    also Threading

    old

    Code
    start_new_thread(self.downloadEvents, ())

    Uses start_new_thread from the _thread module (commented alternative: import _thread).



    new

    Code
    Thread(target=self.downloadEvents).start()


    Uses the threading.Thread class (assuming from threading import Thread).Reason: The threading module is the standard, high-level API for threading in Python, replacing the low-level _thread module. It provides better control and is more maintainable.

    From my side. I have stopped to support py2. and last edit it is for python 3.13.5 the old code does not work with py 3.13.5 only with 3.13.4. So I have change it to compatible with py 3.13.5 .


    1- Here in your replay you was said (stopped working)

    and now you saying (I used to enter my city name in both options, and it worked just fine)

    Sometimes you say (stopped working) and sometimes you say (worked just fine) ?!!!!!


    2 - Again and Again And again ... I repeat again what I said before ... That option what I have removed (does not work smoothly with almost cities name just with some cities) So I deleted.


    3- Why you are hiding your city name ?! give me the name of your city I will test it by self.

    dreambox 920 oe 2.5 merlin image

    The 17.7 version of the plugin is installed on my device.

    When I come to the screen, the 17.8 update is shown

    After confirming, the device turns into a green screen, after opening again the update screen and the same error continues


    Code
    Traceback (most recent call last):
      File "/usr/lib/enigma2/python/enigma.py", line 8610, in __call__
        return ret(*args, **kwargs)
      File "/usr/lib/enigma2/python/Plugins/Extensions/RaedQuickSignal/tools/Console.py", line 114, in runFinished
        self.finishedCallback()
    -------
    TypeError: myCallback() takes exactly 2 arguments (1 given)
    ]]>
            </enigma2crashlog>
            <pythonMD5sum>

    Fixed !!!




    I don't know what you are meaning.

    Did you read my previous comment carefully?!


    Using the "Searching by city name" option is best...

    The "Choose from list of city names" option doesn't give the correct result. That's because you're choosing a city name that isn't supported by the weather website. I will be removed from the plugin in the next update, it's useless.

    Of course, it's not possible to unify oscam and ncam...

    And it's not possible to separate the codes and put them in separate files...

    We're talking about C++, not Python ...


    On the contrary, when we think about separating the features found in ncam separately, it will become more complicated during the update and maintenance phase...


    As for me, I don't support oscam at all. As you know, my support is only for ncam... You can discuss this matter in a separate thread covering all emojis...


    Here, I only support ncam, and I have no future intention of creating a new, separate project... Because ncam is essentially an independent project from oscam. It's built on the oscam source code, but it has become independent. Why would I go back and rewrite it just to ensure compatibility between the oscam and ncam config files? I have nothing to do with supporting oscam...


    So, I apologize...

    Why?! It doesn't make sense!


    Each imo has its own files to read...

    Also, there are some features in ncam that aren't in oscam, so ncam needs its own files to read them, not oscam


    If you want to unify the files, do it manually... delete the ncam file and create a symlink ... for example, the ncam.conf and oscam.conf files with this command.

    Code
    ln -s /etc/tuxbox/config/oscam.conf /etc/tuxbox/config/ncam.conf

    However, in this case, there will be no support if your ncam doesn't work or doesn't open encrypted channels... you must troubleshoot the errors yourself.


    My ip before active vpn


    Code
    root@dm920:~# wget -qO - http://checkip.amazonaws.com
    77.69.128.93
    root@dm920:~# 


    screenshots for active vpn


    1.jpg


    2.jpg


    3.jpg


    Ip changed fine

    Code
    root@dm920:~# wget -qO - http://checkip.amazonaws.com
    219.100.37.244
    root@dm920:~#