From renato.pontefice at gmail.com Mon Apr 1 11:18:49 2024 From: renato.pontefice at gmail.com (Renato Pontefice) Date: Mon, 1 Apr 2024 17:18:49 +0200 Subject: [moin-user] moin2:How and where to start Message-ID: <0B3D1F3D-CB02-4A2A-A904-22B1D020C979@gmail.com> HI, I?ve installed the moin2 wiki sw on my machine (osx 12.7.4). I?m looking for some documentation about it. Documenting how to start with it and how to continue. I?ve already seen the doc on moin2 but I nevi found doc on: - how to config wikiconfig - how to create a single page . How to merge wiki for (us it with Sphinx) using with ReadTheDoc . Can someone drive me to this doc? Thank you Renato From renato.pontefice at gmail.com Tue Apr 2 07:19:10 2024 From: renato.pontefice at gmail.com (Renato Pontefice) Date: Tue, 2 Apr 2024 13:19:10 +0200 Subject: [moin-user] Integration between moin2 - sphinx, ReadTheDoc Message-ID: Hi, I?m wondering how this 3 tools could be integrated. I mean: I saw that on some page of moin2, there is (at bottom of navigation) a link where, if I push it I can open and manage the way to produce HTML, PDF pub. I saw that this is a ReadTheDoc work (I think) But I?ve already saw that ReadTheDoc accept Sphinx doc (and another format that I think is proprietary). So, do the tools chain is; Moin2(to collect docs)-export in one format that Sphinx can read. Paste the sphinx doc to a ReadTheDoc format? Is this the tools chain? Thank you Renato From crosseyedpenguin at yahoo.com Tue Apr 2 11:51:48 2024 From: crosseyedpenguin at yahoo.com (Roger Haase) Date: Tue, 2 Apr 2024 15:51:48 +0000 (UTC) Subject: [moin-user] moin2:How and where to start In-Reply-To: <0B3D1F3D-CB02-4A2A-A904-22B1D020C979@gmail.com> References: <0B3D1F3D-CB02-4A2A-A904-22B1D020C979@gmail.com> Message-ID: <218286541.4653062.1712073108898@mail.yahoo.com> The instructions for modifying wikiconfig.py are within the wikiconfig.py file. The starting configuration allows read-only access to loaded files so you must make changes to wikiconfig.py to allow write access. There is currently no way to create application docs in moin and upload them directly to readthedocs. I created an issue for you:?https://github.com/moinwiki/moin/issues/1656 On Monday, April 1, 2024 at 08:18:58 AM MST, Renato Pontefice wrote: HI, I?ve installed the moin2 wiki sw on my machine (osx 12.7.4). I?m looking for some documentation about it. Documenting how to start with it and how to continue. I?ve already seen the doc on moin2 but I nevi found doc on: - how to config wikiconfig - how to create a single page . How to merge wiki for (us it with Sphinx) using with ReadTheDoc . Can someone drive me to this doc? Thank you Renato _______________________________________________ moin-user mailing list moin-user at python.org https://mail.python.org/mailman/listinfo/moin-user -------------- next part -------------- An HTML attachment was scrubbed... URL: From crosseyedpenguin at yahoo.com Tue Apr 2 13:53:18 2024 From: crosseyedpenguin at yahoo.com (Roger Haase) Date: Tue, 2 Apr 2024 17:53:18 +0000 (UTC) Subject: [moin-user] Integration between moin2 - sphinx, ReadTheDoc In-Reply-To: References: Message-ID: <1267972140.4735377.1712080398374@mail.yahoo.com> Yes, but someone has to figure out how to make it work. Add future comments to?https://github.com/moinwiki/moin/issues/1656 On Tuesday, April 2, 2024 at 04:19:19 AM MST, Renato Pontefice wrote: Hi, I?m wondering how this 3 tools could be integrated. I mean: I saw that on some page of moin2, there is (at bottom of navigation) a link where, if I push it I can open and manage the way to produce HTML, PDF pub. I saw that this is a ReadTheDoc work (I think) But I?ve already saw that ReadTheDoc accept Sphinx doc (and another format that I think is proprietary). So, do the tools chain is; Moin2(to collect docs)-export in one format that Sphinx can read. Paste the sphinx doc to a ReadTheDoc format? Is this the tools chain? Thank you Renato _______________________________________________ moin-user mailing list moin-user at python.org https://mail.python.org/mailman/listinfo/moin-user -------------- next part -------------- An HTML attachment was scrubbed... URL: From renato.pontefice at gmail.com Fri Apr 12 13:54:07 2024 From: renato.pontefice at gmail.com (Renato Pontefice) Date: Fri, 12 Apr 2024 19:54:07 +0200 Subject: [moin-user] How to start using moinmoin 2 Message-ID: <2DB7AA8C-F641-44DE-96A0-71B93EE136BE@gmail.com> Hi, I?ve installed moinmoin 2 on my Mac OS 12.7. But I?m unable to use it (I?ve used main 1.9 some years ago) Can someone send me a link where I can reach some documentation to use it as a user? Thank you Renato From paul at boddie.org.uk Fri Apr 19 11:27:25 2024 From: paul at boddie.org.uk (Paul Boddie) Date: Fri, 19 Apr 2024 17:27:25 +0200 Subject: [moin-user] Moin 2.0.0a1 released In-Reply-To: <3764218.l3cMcm2LzE@jason> References: <392299705.2775317.1711633964007.ref@mail.yahoo.com> <392299705.2775317.1711633964007@mail.yahoo.com> <3764218.l3cMcm2LzE@jason> Message-ID: <4384569.huGZnxX6fZ@jason> On Friday, 29 March 2024 19:32:50 CEST Paul Boddie wrote: > On Thursday, 28 March 2024 14:52:44 CET Roger Haase via moin-user wrote: > > Moinmoin 2.0.0a1 has been released on > > https://pypi.org/project/moin/#history and > > https://github.com/moinwiki/moin/releases. See > > https://moin-20.readthedocs.io/en/latest/,use > > https://github.com/moinwiki/moin/issues to report bugs. > > Is there a documented way of preparing a Python package from the sources now > that setup.py has been removed? It appears that the Debian pybuild tool available in my distribution version was not new enough to understand pyproject.toml, but a later version of the tool can understand this file. Honestly, I wish that the Python packaging community would just stop changing everything all the time and just focus on delivering a coherent tool that does the job. [...] > If I am going to continue building Debian packages, I need to have a way of > preparing them, so any advice about the latest and greatest in > Python-centric packaging would be very welcome. I managed to work around this change by adjusting the pyproject.toml file to incorporate various data resources that are missing from the built package. This required a new-enough version of setuptools because recursive copying (using "**" notation) had somehow not been implemented until fairly recently. For reference, this missing data resource problem previously affected the setup.py file, and what happens is that various directories inside src/moin, such as static and themes do not have their contents copied to the build hierarchy. I suspect also that the MANIFEST.in file's directives are also not observed. One significant problem with packaging Moin for Debian now revolves around Flask compatibility. Debian unstable has replaced Flask 2 with Flask 3, and despite the corresponding issue being closed in the Moin issue tracker... https://github.com/moinwiki/moin/issues/1659 ...it seems that the code still does not work with Flask 3. Have I missed the changes since 2.0.0a1 that have delivered Flask 3 compatibility? Paul From tw at waldmann-edv.de Fri Apr 19 19:16:03 2024 From: tw at waldmann-edv.de (Thomas Waldmann) Date: Sat, 20 Apr 2024 01:16:03 +0200 Subject: [moin-user] Moin 2.0.0a1 released In-Reply-To: <4384569.huGZnxX6fZ@jason> References: <392299705.2775317.1711633964007.ref@mail.yahoo.com> <392299705.2775317.1711633964007@mail.yahoo.com> <3764218.l3cMcm2LzE@jason> <4384569.huGZnxX6fZ@jason> Message-ID: <2f5cb59d-cfcb-417a-82fa-c22c393cebe4@waldmann-edv.de> Hi Paul, >> Is there a documented way of preparing a Python package from the sources now >> that setup.py has been removed? pip install build cd moin-git-workdir python -m build > Honestly, I wish that the Python packaging > community would just stop changing everything all the time and just focus on > delivering a coherent tool that does the job. Yeah, it can be confusing. But it seems to be consensus that one wants to get rid of executing code in setup.py - except for the cases it is still needed (e.g. when having to build C extensions for Python - we don't need that for moin). >> If I am going to continue building Debian packages, I need to have a way of >> preparing them, so any advice about the latest and greatest in >> Python-centric packaging would be very welcome. I think you can follow 2 approaches: a) start from our sdist (as available from pypi or also from github releases IF you download the correct file there). that can be installed using pip and should work correctly - if not, file a bug please. the sdist has version and manifest information baked in. b) if you prefer to start from source code, you must use git and a non-shallow repo clone (including tags) because we use setuptools_scm to determine the code version from git tags and it also builds the manifest from git committed files. Trying anything else will likely fail or lead to strange problems with the project version or with files missing. > One significant problem with packaging Moin for Debian now revolves around > Flask compatibility. Debian unstable has replaced Flask 2 with Flask 3, and > despite the corresponding issue being closed in the Moin issue tracker... > > https://github.com/moinwiki/moin/issues/1659 > > ...it seems that the code still does not work with Flask 3. Have I missed the > changes since 2.0.0a1 that have delivered Flask 3 compatibility? I did that fix back then and did not notice anything not working (i tested using a developer setup). If you correctly installed moin (please rather use the sdist for that purpose or a developer setup), please file a bug on github with the details. Cheers, Thomas -- GPG Fingerprint: 6D5B EF9A DD20 7580 5747 B70F 9F88 FB52 FAF7 B393 Encrypted E-Mail is preferred / Verschluesselte E-Mail wird bevorzugt. From paul at boddie.org.uk Fri Apr 19 19:58:54 2024 From: paul at boddie.org.uk (Paul Boddie) Date: Sat, 20 Apr 2024 01:58:54 +0200 Subject: [moin-user] Moin 2.0.0a1 released In-Reply-To: <2f5cb59d-cfcb-417a-82fa-c22c393cebe4@waldmann-edv.de> References: <392299705.2775317.1711633964007.ref@mail.yahoo.com> <4384569.huGZnxX6fZ@jason> <2f5cb59d-cfcb-417a-82fa-c22c393cebe4@waldmann-edv.de> Message-ID: <2022833.mZHpG7TUu5@jason> On Saturday, 20 April 2024 01:16:03 CEST Thomas Waldmann wrote: > > I think you can follow 2 approaches: > > a) start from our sdist (as available from pypi or also from github > releases IF you download the correct file there). that can be installed > using pip and should work correctly - if not, file a bug please. the > sdist has version and manifest information baked in. I can't see any releases here: https://github.com/moinwiki/moin Or, indeed, at PyPI. Can you provide some URLs? > b) if you prefer to start from source code, you must use git and a > non-shallow repo clone (including tags) because we use setuptools_scm to > determine the code version from git tags and it also builds the manifest > from git committed files. > > Trying anything else will likely fail or lead to strange problems with > the project version or with files missing. For Debian, it might be acceptable, maybe even desirable, to start from released source archives. Otherwise, working from the upstream repository is probably the best approach. I have been using a traditional repository clone and then invoking the Python packaging tools via the Debian wrappers. There are certainly problems that have arisen, some of them related to the Python tools wanting to dynamically download dependencies, so things like setuptools_scm can cause difficulties if the setup (or pyproject) specifies them. The actual dependencies are generally provided as Debian build dependencies instead, so the Python tools should not need to download and install things. [Flask 3] > I did that fix back then and did not notice anything not working (i > tested using a developer setup). If you correctly installed moin (please > rather use the sdist for that purpose or a developer setup), please file > a bug on github with the details. Investigating this further, I found that it was related to flask-theme which I have now updated to 0.3.6. Unfortunately, more work is needed to get "moin create-instance" to work again, this time related to an absence of help files which are not specified as package data in pyproject.toml. Would you like some suggestions for changes to pyproject.toml? Paul From paul at boddie.org.uk Sat Apr 20 12:13:55 2024 From: paul at boddie.org.uk (Paul Boddie) Date: Sat, 20 Apr 2024 18:13:55 +0200 Subject: [moin-user] Moin 2.0.0a1 released In-Reply-To: <2022833.mZHpG7TUu5@jason> References: <392299705.2775317.1711633964007.ref@mail.yahoo.com> <2f5cb59d-cfcb-417a-82fa-c22c393cebe4@waldmann-edv.de> <2022833.mZHpG7TUu5@jason> Message-ID: <25202548.ssoGhoaoca@jason> On Saturday, 20 April 2024 01:58:54 CEST Paul Boddie wrote: > > Investigating this further, I found that it was related to flask-theme which > I have now updated to 0.3.6. Unfortunately, more work is needed to get > "moin create-instance" to work again, this time related to an absence of > help files which are not specified as package data in pyproject.toml. > > Would you like some suggestions for changes to pyproject.toml? It appears that the patterns in pyproject.toml are incomplete with respect to the templates, omitting the JavaScript files in the templates hierarchy. Further testing and investigation revealed a new dependency - mdx-wikilink- plus - which I have tentatively packaged for Debian, but I now get the following errors when deploying a wiki using Apache and mod_wsgi: File "/usr/lib/python3/dist-packages/moin/themes/__init__.py", line 831, in setup_jinja_env "item_name": request.view_args.get("item_name", ""), ^^^^^^^^^^^^^^^^^^^^^ AttributeError: 'NoneType' object has no attribute 'get' Using the built-in Web server with "moin run" works fine, however. Does this look in any way familiar to anyone? Paul