OK, I tried these steps 1. Visit https://www.python.org/downloads/macos/ and download the latest python release 2. Open Finder and navigate to Applications > Python 3.12 (or whatever version you downloaded) 3. Double click on Update Shell Profile.command to make sure your computer knows where to find Python 4. Open Finder and navigate to Applications > Utilities > Terminal 5. In the Terminal window, type in "pip3 install mnemosyne-proj" and hit Enter 6. A bunch of text will scroll by. Wait until it's done, then type "mnemosyne" and hit Enter
It all seems to work! I'm not sure if the fact that I have XCode helped so it would be good to find a guinea pig. It found my existing database so everything is compatible with the previous version. We could create a file that acts as a launcher for Mnemosyne - attaching an example. Or we could get more fancy and do a full Installer script like the attached. Then the steps would be as simple as 1. Visit https://www.python.org/downloads/macos/ and download the latest python release 2. Download and double click to run Mnemosyne-Installer-MacOS.command 3. Open Finder and navigate to Applications > Mnemosyne.command and double click to run it. I tried to attach the files but Google Groups blocks it. Here's the file contents Mnemosyne.command: ``` mnemosyne ``` Mnemosyne-Installer-MacOS.command ``` #!/bin/bash # This installer pulls mnemosyne from the pip registry. It requires that you have Python installed via https://www.python.org/downloads/macos # make sure python is installed properly and accessible /Applications/Python*/Update\ Shell\ Profile.command # create some helpful launchers on the Desktop echo << EOF > /Applications/Mnemosyne.command mnemosyne EOF echo << EOF > /Applications/Mnemosyne-updater.command pip3 install --upgrade mnemosyne-proj EOF chmod +x ~/Mnemosyne.command /Applications/Mnemosyne-updater.command /Applications/Mnemosyne-updater.command # the actual install happens via this command ``` On Thu, Nov 2, 2023 at 11:06 AM Peter Bienstman <peter.bienst...@gmail.com> wrote: > One should now also be able to do 'pip install mnemosyne-proj'. Would be > good to check this on OSX without homebrew. > > Cheers, > > Peter > > On Thursday, 2 November 2023 at 10:11:09 UTC+1 ace.z.a...@gmail.com wrote: > >> Probably so. >> >> If if ever the same error happens... well I did notice that the error is >> arising from the possibility that pip was run using python3.8, re: >> /tmp/pip-build-env-wqkglcan/overlay/lib/python3.8/...? the sip package >> under python3.8 might be deprecated. This the same error happens, i think >> you can force a different python version using: python3.11 -m pip >> install ... >> >> To update the command it would be: `python3.11 -m pip3 install *--index-url >> https://test.pypi.org/simple/ <https://test.pypi.org/simple/> >> --extra-index-url https://pypi.org/simple/ <https://pypi.org/simple/> * >> mnemosyne==2.10.1.2` >> >> On Thursday, November 2, 2023 at 5:04:24 PM UTC+8 Peter Bienstman wrote: >> >>> That same command in a virtual env gave the error below. I don't think >>> it makes sense to look into this until we've tried putting it on >>> regular pypi. >>> >>> Cheers, >>> >>> Peter >>> >>> Collecting pyqt6<7.0.0,>=6.5.1 >>> Using cached PyQt6-6.6.0.tar.gz (1.0 MB) >>> Installing build dependencies ... done >>> Getting requirements to build wheel ... done >>> Preparing wheel metadata ... error >>> ERROR: Command errored out with exit status 1: >>> command: /home/pbienst/test_env/bin/python /tmp/tmpkp2w15bm >>> prepare_metadata_for_build_wheel /tmp/tmp58kai8sh >>> cwd: /tmp/pip-install-i2hosebo/pyqt6 >>> Complete output (26 lines): >>> Querying qmake about your Qt installation... >>> Traceback (most recent call last): >>> File "/tmp/tmpkp2w15bm", line 126, in prepare_metadata_for_build_wheel >>> hook = backend.prepare_metadata_for_build_wheel >>> AttributeError: module 'sipbuild.api' has no attribute >>> 'prepare_metadata_for_build_wheel' >>> >>> During handling of the above exception, another exception occurred: >>> >>> Traceback (most recent call last): >>> File "/tmp/tmpkp2w15bm", line 280, in <module> >>> main() >>> File "/tmp/tmpkp2w15bm", line 263, in main >>> json_out['return_val'] = hook(**hook_input['kwargs']) >>> File "/tmp/tmpkp2w15bm", line 130, in prepare_metadata_for_build_wheel >>> return _get_wheel_metadata_from_wheel(backend, metadata_directory, >>> File "/tmp/tmpkp2w15bm", line 159, in _get_wheel_metadata_from_wheel >>> whl_basename = backend.build_wheel(metadata_directory, config_settings) >>> File >>> "/tmp/pip-build-env-wqkglcan/overlay/lib/python3.8/site-packages/sipbuild/api.py", >>> >>> line 46, in build_wheel >>> project = AbstractProject.bootstrap('wheel', >>> File >>> "/tmp/pip-build-env-wqkglcan/overlay/lib/python3.8/site-packages/sipbuild/abstract_project.py", >>> >>> line 87, in bootstrap >>> project.setup(pyproject, tool, tool_description) >>> File >>> "/tmp/pip-build-env-wqkglcan/overlay/lib/python3.8/site-packages/sipbuild/project.py", >>> >>> line 602, in setup >>> self.update(tool) >>> File "/tmp/pip-install-i2hosebo/pyqt6/project.py", line 163, in update >>> raise UserException( >>> sipbuild.exceptions.UserException >>> ---------------------------------------- >>> ERROR: Command errored out with exit status 1: >>> /home/pbienst/test_env/bin/python /tmp/tmpkp2w15bm >>> prepare_metadata_for_build_wheel /tmp/tmp58kai8sh Check the logs for >>> full command output. >>> >>> On Thu, Nov 2, 2023 at 9:55 AM Ace Alba <ace.z.a...@gmail.com> wrote: >>> > >>> > For head's up purposes, this command worked on my end: >>> > >>> > "'pip3 install --index-url https://test.pypi.org/simple/ >>> --extra-index-url https://pypi.org/simple/ mnemosyne==2.10.1.2" >>> > >>> > I did use a virtual environment before this command though. >>> > >>> > On Thursday, November 2, 2023 at 4:41:53 PM UTC+8 Ace Alba wrote: >>> >> >>> >> Also I am too unfamiliar with macos to see if homebrew is needed. >>> based from the tutorials i've seen, it is preferred but it is not >>> necessary. As to whether the pip command, even with the --extra-index-url >>> flag, using the official build from the python website, will work... >>> remains to be tested. It think with the --extra-index-url flag it should. >>> >> >>> >> On Thursday, November 2, 2023 at 4:33:38 PM UTC+8 Ace Alba wrote: >>> >>> >>> >>> Wouldn't just uploading the build directly to pypi be a sufficient >>> workaround instead, re the poetry team's response to the build? Tag a build >>> as 2.10.1a0 or something, and debug the package from there when it arise, >>> and once done, just update the build, like to 2.10.1a1? >>> >>> >>> >>> Though we know that test.pypi is a recommended way of testing a >>> build to the repository, it appears that not all dependencies are willing >>> to upload a copy of their project to test.pypi, such as the response of the >>> poetry team to the bug report. even if for some reason we end up resolving >>> the bug with python-poetry on test.pypi, it is definitely likely that we >>> will encounter the same errors with our other dependencies. >>> >>> >>> >>> Or we could wait for devin to run 'pip3 install --index-url >>> https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ >>> mnemosyne==2.10.1a0' in his macbook for us to move forward. Either way we >>> will eventually upload a build to pypi, and this path is the only way to >>> test run the simpler, more familiar version of the pip3 install command. >>> >>> >>> >>> On Wednesday, November 1, 2023 at 5:18:17 PM UTC+8 Peter Bienstman >>> wrote: >>> >>>> >>> >>>> After linux users reported a similar issue, I tried to dig a bit >>> deeper into what was going on, but I ended up submitting a bug report to >>> poetry here: https://github.com/python-poetry/poetry/issues/8601 >>> >>>> >>> >>>> Cheers, >>> >>>> >>> >>>> Peter >>> >>>> >>> >>>> On Monday, 23 October 2023 at 06:38:21 UTC+2 Peter Bienstman wrote: >>> >>>>> >>> >>>>> Thanks for looking into this, but do we really need homebrew? >>> Can't we just use the regular Python install, which would also be easier >>> for users? >>> >>>>> >>> >>>>> Peter >>> >>>>> >>> >>>>> On Sun, 22 Oct 2023, 23:35 Ace Alba, <ace.z.a...@gmail.com> >>> wrote: >>> >>>>>> >>> >>>>>> I've tried looking into this. The following github issue may be >>> relevant: >>> >>>>>> >>> >>>>>> >>> https://github.com/python-poetry/install.python-poetry.org/issues/24 >>> >>>>>> >>> >>>>>> There is a contrast between how python is setup in homebrew >>> versus how the team coded poetry. Based from what I understood so far there >>> are two solutions: >>> >>>>>> >>> >>>>>> 1. Use a virtual environment before pip install. See the >>> following excerpt from one of the maintainers: >>> >>>>>> >>> >>>>>> We provide no support for Homebrew installations; feel free to >>> use Homebrew, but please don't open issues against Poetry unless you have >>> reproduced on an install using this script/pipx/pip+venv. pipx and pip+venv >>> work just fine with framework-based Pythons; #79 complicates the fix I had >>> in mind for this issue, and I will need to spend some time reworking it >>> with the new information in mind (or, we may just drop --copies entirely). >>> >>>>>> >>> >>>>>> 2. Use the following one-liner before going with the Pip install: >>> >>>>>> >>> >>>>>> ``` >>> >>>>>> curl -sSL https://install.python-poetry.org | sed >>> 's/symlinks=False/symlinks=True/' | python3 - >>> >>>>>> ``` >>> >>>>>> >>> >>>>>> This one-liner relates to @ikebo and @ralexx's temporary patch to >>> this issue, which involves a symlink configuration. >>> >>>>>> >>> >>>>>> >>> >>>>>> On Sunday, October 15, 2023 at 3:21:32 PM UTC+8 Peter Bienstman >>> wrote: >>> >>>>>>> >>> >>>>>>> Do people really need homebrew and XCode? Can't they get Python >>> >>>>>>> directly from https://www.python.org/downloads/macos/? >>> >>>>>>> >>> >>>>>>> As for the error, perhaps an easier to debug option would be to >>> see >>> >>>>>>> what happens if you don't use pip yet, but follow the new build >>> >>>>>>> instructions from Ace, which will use poetry to install >>> Mnemosyne in >>> >>>>>>> your system? If that has a similar error, then you could add >>> e.g. >>> >>>>>>> extra print statements to >>> >>>>>>> /python3.11/site-packages/poetry/core/pyproject/toml.py to >>> figure out >>> >>>>>>> what part of the configuration file causes errors? >>> >>>>>>> >>> >>>>>>> Peter >>> >>>>>>> >>> >>>>>>> On Sun, Oct 15, 2023 at 1:50 AM de...@callysto.com < >>> de...@callysto.com> wrote: >>> >>>>>>> > >>> >>>>>>> > Sorry, missed the updates to this thread. Installing XCode, >>> homebrew, python, and pip is a bit of work for non-tech, but assuming we >>> could simplify that I tried running the install command from >>> https://test.pypi.org/project/mnemosyne/2.10.1a0/ and I got the >>> following error output >>> >>>>>>> > >>> >>>>>>> > ``` >>> >>>>>>> > orpved2:~ devin$ pip3 install -i https://test.pypi.org/simple/ >>> mnemosyne==2.10.1a0 >>> >>>>>>> > Looking in indexes: https://test.pypi.org/simple/ >>> >>>>>>> > Collecting mnemosyne==2.10.1a0 >>> >>>>>>> > Downloading >>> https://test-files.pythonhosted.org/packages/fb/4d/d17f2eaead745b10676d4b5795ff3ac8948b685a4b5d61440213ab95af65/mnemosyne-2.10.1a0.tar.gz >>> (898 kB) >>> >>>>>>> > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 898.4/898.4 kB 10.2 >>> MB/s eta 0:00:00 >>> >>>>>>> > Installing build dependencies ... done >>> >>>>>>> > Getting requirements to build wheel ... done >>> >>>>>>> > Preparing metadata (pyproject.toml) ... error >>> >>>>>>> > error: subprocess-exited-with-error >>> >>>>>>> > >>> >>>>>>> > × Preparing metadata (pyproject.toml) did not run >>> successfully. >>> >>>>>>> > │ exit code: 1 >>> >>>>>>> > ╰─> [18 lines of output] >>> >>>>>>> > Traceback (most recent call last): >>> >>>>>>> > File >>> "/usr/local/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", >>> line 353, in <module> >>> >>>>>>> > main() >>> >>>>>>> > File >>> "/usr/local/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", >>> line 335, in main >>> >>>>>>> > json_out['return_val'] = hook(**hook_input['kwargs']) >>> >>>>>>> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> >>>>>>> > File >>> "/usr/local/lib/python3.11/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", >>> line 149, in prepare_metadata_for_build_wheel >>> >>>>>>> > return hook(metadata_directory, config_settings) >>> >>>>>>> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> >>>>>>> > File >>> "/private/var/folders/s_/kfjzrd0x21502lph7nw_nqk80000gr/T/pip-build-env-t6ye3_dd/overlay/lib/python3.11/site-packages/poetry/core/masonry/api.py", >>> line 40, in prepare_metadata_for_build_wheel >>> >>>>>>> > poetry = Factory().create_poetry(Path(".").resolve(), >>> with_groups=False) >>> >>>>>>> > >>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> >>>>>>> > File >>> "/private/var/folders/s_/kfjzrd0x21502lph7nw_nqk80000gr/T/pip-build-env-t6ye3_dd/overlay/lib/python3.11/site-packages/poetry/core/factory.py", >>> line 46, in create_poetry >>> >>>>>>> > local_config = PyProjectTOML(path=poetry_file).poetry_config >>> >>>>>>> > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ >>> >>>>>>> > File >>> "/private/var/folders/s_/kfjzrd0x21502lph7nw_nqk80000gr/T/pip-build-env-t6ye3_dd/overlay/lib/python3.11/site-packages/poetry/core/pyproject/toml.py", >>> line 74, in poetry_config >>> >>>>>>> > assert isinstance(config, Table) >>> >>>>>>> > AssertionError >>> >>>>>>> > [end of output] >>> >>>>>>> > >>> >>>>>>> > note: This error originates from a subprocess, and is likely >>> not a problem with pip. >>> >>>>>>> > error: metadata-generation-failed >>> >>>>>>> > >>> >>>>>>> > × Encountered error while generating package metadata. >>> >>>>>>> > ╰─> See above for output. >>> >>>>>>> > >>> >>>>>>> > note: This is an issue with the package mentioned above, not >>> pip. >>> >>>>>>> > hint: See above for details. >>> >>>>>>> > ``` >>> >>>>>>> > >>> >>>>>>> > Not sure yet if this is my setup or a generic issue. I don't >>> get the same error with, for example, pip3 install sphinx >>> >>>>>> >>> >>>>>> -- >>> >>>>>> >>> >>>>>> You received this message because you are subscribed to the >>> Google Groups "mnemosyne-proj-users" group. >>> >>>>>> To unsubscribe from this group and stop receiving emails from it, >>> send an email to mnemosyne-proj-u...@googlegroups.com. >>> >>>>>> >>> >>>>>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/mnemosyne-proj-users/bf3742f7-4694-435a-ac24-3183df0847f1n%40googlegroups.com. >>> >>> > >>> > -- >>> > You received this message because you are subscribed to the Google >>> Groups "mnemosyne-proj-users" group. >>> > To unsubscribe from this group and stop receiving emails from it, send >>> an email to mnemosyne-proj-u...@googlegroups.com. >>> > To view this discussion on the web visit >>> https://groups.google.com/d/msgid/mnemosyne-proj-users/89ea4e79-529d-45e9-a95b-45787646577en%40googlegroups.com. >>> >>> >> -- > You received this message because you are subscribed to a topic in the > Google Groups "mnemosyne-proj-users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/mnemosyne-proj-users/ah7zdRHLhcg/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > mnemosyne-proj-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/mnemosyne-proj-users/81a7821c-1cf9-463e-b0a7-db92968daf43n%40googlegroups.com > <https://groups.google.com/d/msgid/mnemosyne-proj-users/81a7821c-1cf9-463e-b0a7-db92968daf43n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to mnemosyne-proj-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/mnemosyne-proj-users/CAKr60uMGo0Jp6dERhQ-LBAxR9uHMwGHLr%3DoN%3Dsvwgucknf1iuA%40mail.gmail.com.
