New Release pyILPER 1.8.3

[jsi]

Version 1.8.3 of the pyILPER software is available as from now.

This release fixes some minor bugs in the graphical user interface of the drive tab. See the Release Announcement for details.

Notice to users of the Anaconda/Miniconda platform:

Meanwhile, the Anaconda/Miniconda platform finished the transition to version 3.8 of the Python Interpreter. Therefore, the new pyILPER version is only available if your Anaconda/Miniconda environment is up to date. If you do not get the new pyILPER version then please upgrade your Python version first. If the Anaconda/Miniconda console shortcuts get lost during the installation on Windows, please follow the instructions in this post.

See the Installation instructions how to upgrade.

Regards
Joachim

[ThomasF]

Hi Joachim!

This looks amazing - I must give it a try!

EDIT:
After a "clean" install on my Ubuntu machine, the application failed (see below).
After some debugging and googling I found a solution to my problem:
Installing Qt5 on Ubuntu needs some OpenGL libraries, so the following update fixed my problem:

Code:

sudo apt-get install mesa-common-dev

Now it seems to work!

----------------

But, I tried to follow you installation process on a Ubuntu 20.04 machine with Python 3.8 installed.
I followed the Anaconda installation guide without any problems, but the application fails during startup.

The applications main window opens and I get a dialog saying:
"Serial device not configured: Run pyILper configuration"
and a OK-button, but as soon as I press the OK-button, the application crashes and exits:
"Segmentation fault - memory dump created"
so I never get a chance to run the configuration ...

/var/log/kernel.log:

Code:

Jan 12 11:53:28 MossaDev kernel: [ 2336.541767] python3.8[8646]: segfault at 0 ip 0000000000000000 sp 00007ffdd8985d18 error 14 in python3.8[55ba287bf000+5f000]
Jan 12 11:53:28 MossaDev kernel: [ 2336.541772] Code: Bad RIP value.

/var/log/apport.log:

Code:

ERROR: apport (pid 8680) Tue Jan 12 11:53:28 2021: called for pid 8646, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 8680) Tue Jan 12 11:53:28 2021: script: /home/thomas/tools/miniconda3/bin/pyilper, interpreted by /home/thomas/tools/miniconda3/bin/python3.8 (command line "/home/thomas/tools/miniconda3/bin/python /home/thomas/tools/miniconda3/bin/pyilper")
ERROR: apport (pid 8680) Tue Jan 12 11:53:28 2021: executable does not belong to a package, ignoring

The PIL-Box is there (/dev/ttyUSB0) and I can access it - so apparently no access faults on the port ...

Same behaviour if I clone the git repository and starts with start.py instead.

Any ideas how I could debug or find out what is missing or failing for me? Smells like something outside of your application ...

Cheers,
Thomas

[jsi]

Hi Thomas,

I did a clean installation of Miniconda and pyILper on my KDE-Neon 20.04 machine (which bases on Ubuntu 20.04) and had no issues. According to this source
the packages mesa-common-dev and libglu1-mesa-dev are needed to run QT5 on Ubuntu. Interestingly only libglu1-mesa-dev is installed on my system.

I think this pitfall exists, if Qt5 of Anaconda/Miniconda is installed without a prior installation of the Qt5 libraries which the Linux distribution provides.

Regards
Joachim

[rprosperi]

I'm having trouble updating Anaconda, wonder if you could suggest something?

I did the following:

(base) path> conda update conda

(base) path> conda update --all

but pyilper was not updated.

If I now do conda list, I get:

Code:

# packages in environment at C:\Miniconda3:
#
# Name                    Version                   Build  Channel
brotlipy                  0.7.0           py37h2bbff1b_1003
ca-certificates           2020.12.8            haa95532_0
certifi                   2020.12.5        py37haa95532_0
cffi                      1.14.4           py37hcd4344a_0
chardet                   4.0.0           py37haa95532_1003
conda                     4.9.2            py37haa95532_0
conda-package-handling    1.7.2            py37h76e460a_0
cryptography              3.3.1            py37hcd4344a_0
icu                       58.2                 ha925a31_3
idna                      2.10                       py_0
jpeg                      9b                   hb83a4c4_2
libpng                    1.6.37               h2a8f88b_0
menuinst                  1.4.16           py37he774522_1
openssl                   1.1.1i               h2bbff1b_0
pip                       20.3.3           py37haa95532_0
pycosat                   0.6.3            py37h2bbff1b_0
pycparser                 2.20                       py_2
pyilper                   1.8.2                    py37_0    bug400
pyopenssl                 20.0.1             pyhd3eb1b0_1
pyqt                      5.9.2            py37h6538335_2
pyserial                  3.5              py37haa95532_0
pysocks                   1.7.1                    py37_1
python                    3.7.9                h60c2a47_0
pywin32                   227              py37he774522_1
qt                        5.9.7            vc14h73c81de_0
requests                  2.25.1             pyhd3eb1b0_0
ruamel_yaml               0.15.87          py37he774522_1
setuptools                51.1.2           py37haa95532_4
sip                       4.19.8           py37h6538335_0
six                       1.15.0           py37haa95532_0
sqlite                    3.33.0               h2a8f88b_0
tqdm                      4.55.1             pyhd3eb1b0_0
urllib3                   1.26.2             pyhd3eb1b0_0
vc                        14.2                 h21ff451_1
vs2015_runtime            14.27.29016          h5e58377_2
wheel                     0.36.2             pyhd3eb1b0_0
win_inet_pton             1.1.0            py37haa95532_0
wincertstore              0.2                      py37_0
yaml                      0.2.5                he774522_0
zlib                      1.2.11               h62dcd97_4

I did not see any errors, warnings, etc. it simply seems to not update ilper.

I then tried

(base) path > conda update pyilper

And it reports "# All requested packages already installed."

This is on Win-7 Pro x64 (yes, I know this should be Win-10, but this machine has some s/w which is not Win-10 compatible - hopefully moved to another old machine soon).

[jsi]

You are still running Python 3.7. However pyILPER 1.8.3. requires Python 3.8.

Please update your Anaconda environment to Python 3.8 with:

Code:

conda install python=3.8

And check with

Code:

conda list

if everything went well.

In recent times there were many changes to the Anaconda envrionment on Windows. If the update to Python 3.8 fails then I recommend you to do a clean reinstallation of the Anaconda/Miniconda environment.

Regards
Joachim

[rprosperi]

(01-13-2021 06:53 AM)jsi Wrote:  You are still running Python 3.7. However pyILPER 1.8.3. requires Python 3.8.

Thanks for the instructions, Joachim. Oddly, after updating Anaconda as described above, it appears the update process has removed the Anaconda Command from my start menu entirely, so now there is nowhere to open the Anaconda command prompt window. The folder structure is intact in c:\Miniconda3, but I don't see any (obvious) links for opening the command window.

Could someone please look at their working Miniconda3 setup and let me know the actual file (and arguments, if needed) which is launched when opening the Anaconda Prompt and I'll rebuild a shortcut and start menu entry to go in and attempt this update.

Thanks.

[Dave Frederickson]

(01-14-2021 02:46 PM)rprosperi Wrote:  Could someone please look at their working Miniconda3 setup and let me know the actual file (and arguments, if needed) which is launched when opening the Anaconda Prompt and I'll rebuild a shortcut and start menu entry to go in and attempt this update.

I recently reinstalled Python on my system. This time I only installed Miniconda. It created two shortcuts.

Anaconda Powershell Prompt (miniconda3)
Target: %windir%\System32\WindowsPowerShell\v1.0\powershell.exe -ExecutionPolicy ByPass -NoExit -Command "& 'C:\Users\USERNAME\miniconda3\shell\condabin\conda-hook.ps1' ; conda activate 'C:\Users\USERNAME\miniconda3' "

Anaconda Prompt (miniconda3)
Target: %windir%\System32\cmd.exe "/K" C:\Users\USERNAME\miniconda3\Scripts\activate.bat C:\Users\USERNAME\miniconda3

Dave

[jsi]

(01-14-2021 02:46 PM)rprosperi Wrote:  Oddly, after updating Anaconda as described above, it appears the update process has removed the Anaconda Command from my start menu entirely, so now there is nowhere to open the Anaconda command prompt window. The folder structure is intact in c:\Miniconda3, but I don't see any (obvious) links for opening the command window.

I had this issue some time ago on Windows and solved it with a clean reinstallation of Miniconda. But you can try the following:

• Open a command prompt window
• Change to the directory c:\Miniconda3\scripts
• Run the "activate" command here
• You should see a "(base)" inserted before the command prompt
• Run "conda list" or "pyilper" to verify that your Miniconda Environment is set up properly
• Execute "conda install console_shortcut"
• Check, whether the shortcuts were recreated
  

[rprosperi]

Thanks Dave, but I just fixed it following a post I found in stackoverflow, which created essentially the same Anaconda Prompt.

I found the post here:

https://stackoverflow.com/questions/3413...windows-10

using the steps in the 4th or 5th post down that begins "mkmenus did not work for me but the following worked..."

Once I had the Anaconda Prompt back, Joachim's instructions for updating to Python 3.8 worked perfectly and quickly, updating all components including pyilper.

Thanks Joachim and Thanks Dave!

[Massimo Gnerucci]

(01-14-2021 04:03 PM)rprosperi Wrote:  Thanks Dave, but I just fixed it following a post I found in stackoverflow,

[rprosperi]

There is far more truth in that image than most people are willing to admit... LOL.

Thanks for the cheer Massimo!