[PySide] [Interest] PySide2 installer for windows?

[Frank Rueter | OHUfx]

I do understand, but a few months ago we were able to run this to 
install a PySide2 version that works just fine:

pip install --index-url=http://download.qt.io/snapshots/ci/pyside/5.6/latest/  pyside2 --trusted-host download.qt.io

We only need this for a single inhouse app we use every day and it has 
worked perfectly on the three machines it was installed on.

Now we need it on more machines and the above no longer works.
I didn't want to get into any more complicated issues.

I understand for serious development this is very important, but for us 
it's a single, simple but important tool we can't use easily (except on 
three machines) and I would love to rectify this until I get time to 
adapt the code for python3.

So if anybody has an idea where to find the installer that would have 
been pulled via the above earlier this year I would very much appreciate it.

Cheers,
frank


On 22/05/19 2:53 AM, Cristián Maureira-Fredes wrote:
> Hello,
>
> Just wanted to point out that when you go to:
>
> https://pyside.org
>
> you see a colorful table with the
> compatibility on the different platform and the reason
> behind them being not supported.
>
> I was under the impression that it was the best
> way possible to communicate these release of the
> details, but I think I was mistaken.
>
> Since I don't want this to be a RTFM email,
> I'm honestly asking:
>
> Does anyone has any other more direct way to communicate this?
>
> Maybe people were confused while visiting:
>
> https://www.qt.io/qt-for-python
>
> Should we mention the support there too?
>
> I really would like to know how to communicate this,
> since it's possible that in an unknown period of time
> we will drop support for Python2 (months? years?)
> and then we will need to communicate that with the whole
> community.
>
> Cheers
>
>
> On 5/18/19 8:06 PM, Croitor Alexandru wrote:
>> Hi,
>>
>> Point 1: At the official first release of Qt For Python / PySide2 which
>> was bundled with Qt 5.11, we never provided py27 windows packages. So
>> officially, we haven't dropped any packages, because they weren't there
>> in the first place.
>>
>> Point 2: Packages for py2.7 for PySide2 do not exist not because of py2
>> EoL, but rather because the official py27 interpreter is built with MSVC
>> 2008, whereas Qt is built with MSVC2015, and we deemed that with the
>> current PySide2 codebase, it is not safe to mix MSVC runtimes.
>>
>> This was communicated multiple times, and is mentioned on the wiki as
>> well. Yet people still insist on bringing it up, disregarding that such
>> packages are not safe to use.
>>
>> People are free to try and build Py2.7 + Qt + PySide2 with the same MSVC
>> version, and use that.
>>
>> On Sat, May 18, 2019 at 7:03 PM Thiago Macieira
>> <thiago.macieira at intel.com <mailto:thiago.macieira at intel.com>> wrote:
>>
>>      On Friday, 17 May 2019 18:26:11 PDT Bob Hood wrote:
>>       > On 5/17/2019 2:58 PM, Thiago Macieira wrote:
>>       > > On Friday, 17 May 2019 10:16:04 PDT Bob Hood wrote:
>>       > >> They have (prematurely, imo) abandoned the combination of
>>      Windows +
>>       > >> Python
>>       > >> v2.7.  You will only be able to install PySide2 under Windows
>>      with Python
>>       > >> v3.x now.
>>       > >
>>       > > Less than 7 and a half months of support for Python 2 left,
>>      until it EOLs,
>>       > > after a 5 year extension. Everyone has migrated their business
>>      critical
>>       > > applications to Python 3 by now, right?
>>       >
>>       > Well, to me "7 and a half months...left" is not EOL, and I don't know
>>       > precisely when Python v2/Windows support was jettisoned, but you
>>      can add
>>       > that difference to the duration as well.That's how I personally
>>      define
>>       > "prematurely."
>>
>>      Python2 support was deprecated by the Python community and the
>>      Python Software
>>      Foundation many years ago. Its EOL was pushed from Jan 1, 2015 to
>>      Jan 1, 2020.
>>
>>      The point is not about Pyside, it's about *Python*. People have had
>>      over 10
>>      years to switch from 2.x to 3. With less than 7½ months left, I'm sure
>>      everyone with critical applications have already switch, right?
>>
>>      https://pythonclock.org/
>>
>>       > But the decision is made; I'm not instigating a brush war over
>>      it.  I'm not
>>       > invested in PySide2, and neither are my customers. It was just
>>      going to be a
>>       > convenience for them as long as we continued to support Python
>>      v2.  Now it
>>       > won't.
>>
>>      I think the point is that it's not worth the resources required to
>>      build and
>>      test the Python2 bulld when so few are (supposed to be) still using it.
>>
>>      --
>>      Thiago Macieira - thiago.macieira (AT) intel.com <http://intel.com>
>>         Software Architect - Intel System Software Products
>>
>>
>>
>>      _______________________________________________
>>      Interest mailing list
>>      Interest at qt-project.org <mailto:Interest at qt-project.org>
>>      https://lists.qt-project.org/listinfo/interest
>>
>>
>> _______________________________________________
>> Interest mailing list
>> Interest at qt-project.org
>> https://lists.qt-project.org/listinfo/interest
>>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20190523/2584b01f/attachment.html>