Can you add a test?

I see#1374

I tried testing this with the latest 2.5.2 release. Could it be that there was something wrong with the distribution of the package? We checked on multiple environments and it looks like when we install 2.5.2 we still get 2.5.1. Really odd but we're running out of ideas of what we might be doing wrong for a straight forward upgrade... :-) Also tried fresh installs...

For example:

PS C:\Users\user> pip install --upgrade pythonnet==2.5.2Collecting pythonnet==2.5.2  Downloading https://files.pythonhosted.org/packages/0c/b3/e136267c9299ac5572286ccb807f4b0a6bad9b882e7ca94691004a6acc83/pythonnet-2.5.2-cp36-cp36m-win_amd64.whl (81kB)     |████████████████████████████████| 92kB 737kB/sRequirement already satisfied, skipping upgrade: pycparser in c:\users\apaganini\appdata\local\programs\python\python36\lib\site-packages (from pythonnet==2.5.2) (2.20)Installing collected packages: pythonnet  Found existing installation: pythonnet 2.5.1    Uninstalling pythonnet-2.5.1:      Successfully uninstalled pythonnet-2.5.1Successfully installed pythonnet-2.5.2WARNING: You are using pip version 19.3.1; however, version 21.0.1 is available.You should consider upgrading via the 'python -m pip install --upgrade pip' command.PS C:\Users\user> pyPython 3.6.5 (v3.6.5:f59c0932b4, Mar 28 2018, 17:00:18) [MSC v.1900 64 bit (AMD64)] on win32Type "help", "copyright", "credits" or "license" for more information.>>> import clr>>> clr.__version__'2.5.1'

It's possible that I missed one version string somewhere, sorry about that. The process on the backports branch is completely manual.

Thank you@filmor - what's the path forward? is it going to be re-released as 2.5.2 or changed to 2.5.3? i.e. - will I get notified of a new release when this is corrected?

@filmor I apologize but I actually commented on the wrong issue. It was supposed to be on#1364 - But regardless looks like something in the distribution is wrong based on the above comment.

I don't intend to do a 2.5.3 release just for this. 2.5 is frozen, only patches for regressions are backported. Work is happening onmaster. The issue you wanted to comment on is not merged into backports-2.5 anyway.