Thanks Vasily. I did have one more thing I tried $ wget --no-verbose https://files.pythonhosted.org/packages/d0/f7/56e35902d32299020cf9136264ca102ff0b03c0555621b469c825bc10d08/pypiwin32-220-cp36-none-win_amd64.whl && python3 -m pip install pypiwin32-220-cp36-none-win_amd64.whl pypiwin32-220-cp36-none-win_amd64.whl is not a supported wheel on this platform.
I tried the 32 bit version too. Python version is 3.6.2, so I'm not sure why it won't let me use that wheel. On Sat, Apr 28, 2018 at 3:34 PM, Vasily Galkin <[email protected]> wrote: > I'm very sorry by not mentioning this earlier but pywin32 is NOT hard > dependency for building meld installer, it's an *optional* dependency of > cxFreeze. > In the pygobject-win32 build it is only used for writing version info into > exe file headers, which is useful, but not required at all. > > So building installer without it would be quite fine! > > The bad thing about msys2 - is the random-hangs bug > https://gitlab.gnome.org/GNOME/meld/issues/174 > > > Oh, one last thing I forgot to mention is that there's currently no > package for pywin32 in the MSYS2 repos either. > > > > On Sat, Apr 28, 2018 at 3:19 PM, Keegan Witt <[email protected]> > wrote: > > > >> I'm having trouble getting pywin32 installed in MSYS2. When I try to > install with pip, I get errors$ python3 -m pip install pypiwin32==219 > >> Collecting pypiwin32==219 > >> Using cached https://files.pythonhosted.org/packages/2b/ca/ > 5c086c18de8f70222787b3e824e755b68d99272531522e77bb381d4f60c8 > /pypiwin32-219.zip > >> Complete output from command python setup.py egg_info: > >> Traceback (most recent call last): > >> File "<string>", line 1, in <module> > >> File "/tmp/pip-install-d9xe2c9w/pypiwin32/setup.py", line 121 > >> print "Building pywin32", pywin32_version > >> ^ > >> SyntaxError: Missing parentheses in call to 'print' > >> > >> ---------------------------------------- > >> Command "python setup.py egg_info" failed with error code 1 in > /tmp/pip-install-d9xe2c9w/pypiwin32/ > >> > >> $ python3 -m pip install pypiwin32==223 > >> > >> Collecting pypiwin32==223 > >> Using cached https://files.pythonhosted.org/packages/d0/1b/ > 2f292bbd742e369a100c91faa0483172cd91a1a422a6692055ac920946c5 > /pypiwin32-223-py3-none-any.whl > >> Collecting pywin32>=223 (from pypiwin32==223) > >> Could not find a version that satisfies the requirement pywin32>=223 > (from pypiwin32==223) (from versions: ) > >> No matching distribution found for pywin32>=223 (from pypiwin32==223) > >> > >> Downloading and installing outside pip isn't an option because > distutils doesn't support silent installs (https://github.com/mhammond/ > pywin32/issues/845). If you run the command locally, you can see it pops > up the GUI installer. > >> $ wget --no-verbose --output-document=pywin32.exe > https://github.com/mhammond/pywin32/releases/download/ > b223/pywin32-223.win-amd64-py3.6.exe && ./pywin32.exe && rm pywin32.exe > >> > >> We could try compiling pywin32 from source, but it looks like it might > be complicated. > >> > >> On Wed, Mar 28, 2018 at 12:54 AM, Keegan Witt <[email protected]> > wrote: > >> > >>> When I do python --version, I get "Python 3.6.2" (and that's the > version I see pacman downloaded). I think maybe the AIO installer is > installing some stuff I don't have in pacman yet. > >>> > >>> On Tue, Mar 27, 2018 at 5:30 PM Kai Willadsen <[email protected]> > wrote: > >>> > >>>> Probably not super-helpful, but I notice that you're just using > >>>> > >>>> `python` there, which seems to be defaulting to Python 2.7, whereas we > >>>> > >>>> definitely want 3.x for current Meld. > >>>> > >>>> Either way, I'm really happy for others to be looking at this. > >>>> > >>>> On 27 March 2018 at 15:16, Keegan Witt <[email protected]> wrote: > >>>> > >>>>> I've started work on a pipeline for msys2 here (but it's not working > yet): > >>>> > >>>>> https://ci.appveyor.com/project/keeganwitt/meld-q7ht3. I dunno if > folks are > >>>> > >>>>> able to see settings I have so far or not, so here they are > >>>> > >>>>> > >>>> > >>>>> version: 3.18.1.{build} > >>>> > >>>>> skip_non_tags: true > >>>> > >>>>> clone_depth: 1 > >>>> > >>>>> environment: > >>>> > >>>>> PATH: C:\msys64\usr\bin;$(PATH) > >>>> > >>>>> install: > >>>> > >>>>> - cmd: >- > >>>> > >>>>> bash -lc "pacman --noconfirm --sync --refresh --refresh pacman" > >>>> > >>>>> > >>>> > >>>>> bash -lc "pacman --noconfirm --sync --refresh --sysupgrade" > >>>> > >>>>> > >>>> > >>>>> bash -lc "pacman --noconfirm -S python mingw-w64-i686-gtk3 > >>>> > >>>>> mingw-w64-x86_64-gtksourceview3 glib2-devel" > >>>> > >>>>> > >>>> > >>>>> rem bash -lc "pip install --upgrade pip" > >>>> > >>>>> > >>>> > >>>>> bash -lc "pip install pypiwin32==219" > >>>> > >>>>> > >>>> > >>>>> bash -lc "pip install cx_Freeze==5.0.2" > >>>> > >>>>> build_script: > >>>> > >>>>> - cmd: bash -lc 'cd "%APPVEYOR_BUILD_FOLDER%" && > glib-compile-schemas data > >>>> > >>>>> && python setup_win32.py bdist_msi' > >>>> > >>>>> > >>>> > >>>>> > >>>> > >>>>> > >>>> > >>>>> On Mon, Mar 26, 2018 at 10:13 PM Kai Willadsen < > [email protected]> > >>>> > >>>>> wrote: > >>>> > >>>>>> > >>>> > >>>>>> On 26 March 2018 at 22:00, Vasily Galkin <[email protected]> > wrote: > >>>> > >>>>>> > About using msys2 binaries instead of pygobject-win32: I'm > running meld > >>>> > >>>>>> > checkout with mingw64 for several months by now. > >>>> > >>>>>> > It contains newer gtk and so shortcuts problems with non-english > >>>> > >>>>>> > keyboards https://gitlab.gnome.org/GNOME/meld/issues/129 is > solved (which is > >>>> > >>>>>> > great!) > >>>> > >>>>>> > > >>>> > >>>>>> > But unfortunately it has a huge problem: nearly 1 of 10 > invocations > >>>> > >>>>>> > hangs on startup. This is very annoying. I just reported and > crosslinked > >>>> > >>>>>> > this as https://github.com/Alexpux/MINGW-packages/issues/3510 and > >>>> > >>>>>> > https://gitlab.gnome.org/GNOME/meld/issues/174 > >>>> > >>>>>> > > >>>> > >>>>>> > Apart from this I had several crashes, but they are extremely > rare (1 > >>>> > >>>>>> > per month with intensive every-day use, like 1 from 1000 usages > leads to > >>>> > >>>>>> > crash). > >>>> > >>>>>> > >>>> > >>>>>> ...and we've been forced on to msys2 by some changes I made to stop > >>>> > >>>>>> supporting older GTK+. I *can* revert these, but I'd really rather > >>>> > >>>>>> not, since we need to (IMO) move to using msys2 sooner rather than > >>>> > >>>>>> later anyway. > >>>> > >>>>>> > >>>> > >>>>>> Kai >
_______________________________________________ meld-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/meld-list
