Re: [Trac] Re: Trac 1.0.19 Released
On 08/01/2020 19:33, Roger Oberholtzer wrote: Is there a guide for the Trac part? Like the obvious things that need to be changed for Trac 1.4? Something with example uses and not just the names of the things to change? The full list of things that need to be changed: https://trac.edgewall.org/wiki/TracDev/ApiChanges/1.3 But very few plugins will be affected by all these. More typical is one or two (or zero!) problems, but not each plugin has the same problems. So typically it's much more efficient to just try the plugin and see if anything is broken. Then create a ticket and ask / figure out why from the error message / looking at the source and comparing the used APIs to the list. Usually it's quite obvious. (At least after you've seen a few cases.) The "obvious" exception is Jinja / Genshi: If the plugin contains HTML templates these need to be converted. The guide for that is here: https://trac.edgewall.org/wiki/TracDev/PortingFromGenshiToJinja A small example of such a conversion for a macro plugin: https://trac-hacks.org/changeset/17465 More examples: https://trac-hacks.org/search?q=jinja=1=on https://trac-hacks.org/search?q=1.4=1=on For very old plugins (pre-1.0) of course more things typically need to be updated. https://trac.edgewall.org/wiki/TracDev/ApiChanges E.g. the most typical problem is probably the deprecated DB APIs: https://trac.edgewall.org/wiki/TracDev/DatabaseApi#Trac1.0API Perhaps the Plugins that only work with Python 2 should be moved to a depreciated location? That might make it easier to see which plugins are effected by a move to Python 3. Since there is no easily testable Python 3 version of Trac yet, I don't think any plugins are known to work / not work in Python 3. It will probably be similar as above: Try it and see if it works etc. I assume the way to push this forward is for someone to update the branch rjollos.git@t12130_python3.1: https://trac.edgewall.org/ticket/12130#comment:51 Simplify it by dropping "six" / Python 2 support, and make sure all tests pass, so it can be considered for applying to trunk, tested and released. Hope this helps, Peter -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/8379ba87-892e-5177-15ad-8311149dc7fb%40gmail.com.
Re: [Trac] Re: Trac 1.0.19 Released
On Fri, Jan 10, 2020 at 7:36 AM Steffen Hoffmann wrote: > >I could help. Except that my python knowledge is not my strong point. > >But I am willing to try. > > Great. Let's join by means of crearing guiding documentation in Trac-hacks > Wiki this coming weekend then! Has there been any start at this kind of thing? Existing stuff to start with? -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CANkOqwNcA5CWyQEj2SEVO%2BzfbaaNcCniD-Q1xZ5YqhR0BF2VAQ%40mail.gmail.com.
Re: [Trac] Re: Trac 1.0.19 Released
Am 9. Januar 2020 08:47:22 MEZ schrieb Roger Oberholtzer : >On Thu, Jan 9, 2020 at 6:10 AM Steffen Hoffmann wrote: > >> >Maybe it's time to enlist support in updating plugins? I'm a >> >programmer, but not a Python programmer. But I could consider >trying >> >a few plugins to update. >> > ... >I could help. Except that my python knowledge is not my strong point. >But I am willing to try. Great. Let's join by means of crearing guiding documentation in Trac-hacks Wiki this coming weekend then! Greetings, Steffen Hoffmann -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/DAC00565-EB4E-492E-A8E2-8BB724724789%40web.de.
Re: [Trac] Re: Trac 1.0.19 Released
On Thu, Jan 9, 2020 at 6:10 AM Steffen Hoffmann wrote: > >Maybe it's time to enlist support in updating plugins? I'm a > >programmer, but not a Python programmer. But I could consider trying > >a few plugins to update. > > > >Is there a guide for the Trac part? Like the obvious things that need > >to be changed for Trac 1.4? Something with example uses and not just > >the names of the things to change? > > I've been reading about Python3 before and right now scanning Trac 1.3 > changes while trying to get AccountManagerPlugin Code ready for current Trac > 1.4. > > After current Trac 1.5 releases Trac 1.6 is meant to switch to Python3. > > I'm willing to share and improve developer instructions as I did some years > before for spread I18n support among plugins too. > > Let‘s do that together. How about that? I could help. Except that my python knowledge is not my strong point. But I am willing to try. -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CANkOqwMD832BBSqYYss2vGCP5nasmU9jggG-p1pvVH4_bXM%3Dng%40mail.gmail.com.
Re: [Trac] Re: Trac 1.0.19 Released
Am 8. Januar 2020 19:33:16 MEZ schrieb Roger Oberholtzer : >On Wed, Jan 8, 2020 at 3:27 PM Martin wrote: >> >> On 2020-01-07 11:04, Roger Oberholtzer wrote: >> > Perhaps the Plugins that only work with Python 2 should be moved to >a >> > depreciated location? That might make it easier to see which >plugins >> > are effected by a move to Python 3. >> >> As a side note: In Debian we are in the process of remving Trac >> and all packaged plugins as part of the "py2removal" process. We >> would like to reintroduce the Python-3-based Trac again, when it >> is ready, of course. > >The list of Plugins for Trac 1.4 at least is much smaller than the >list of all plugins. > >Maybe it's time to enlist support in updating plugins? I'm a >programmer, but not a Python programmer. But I could consider trying >a few plugins to update. > >Is there a guide for the Trac part? Like the obvious things that need >to be changed for Trac 1.4? Something with example uses and not just >the names of the things to change? I've been reading about Python3 before and right now scanning Trac 1.3 changes while trying to get AccountManagerPlugin Code ready for current Trac 1.4. After current Trac 1.5 releases Trac 1.6 is meant to switch to Python3. I'm willing to share and improve developer instructions as I did some years before for spread I18n support among plugins too. Let‘s do that together. How about that? Greetings Steffen Hoffmann -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/8B47C075-7A01-433B-A235-8BA5666E7BE2%40web.de.
Re: [Trac] Re: Trac 1.0.19 Released
On Wed, Jan 8, 2020 at 3:27 PM Martin wrote: > > On 2020-01-07 11:04, Roger Oberholtzer wrote: > > Perhaps the Plugins that only work with Python 2 should be moved to a > > depreciated location? That might make it easier to see which plugins > > are effected by a move to Python 3. > > As a side note: In Debian we are in the process of remving Trac > and all packaged plugins as part of the "py2removal" process. We > would like to reintroduce the Python-3-based Trac again, when it > is ready, of course. The list of Plugins for Trac 1.4 at least is much smaller than the list of all plugins. Maybe it's time to enlist support in updating plugins? I'm a programmer, but not a Python programmer. But I could consider trying a few plugins to update. Is there a guide for the Trac part? Like the obvious things that need to be changed for Trac 1.4? Something with example uses and not just the names of the things to change? -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CANkOqwMyq0qC%3DhpWRpf2933NB3zA8yOA35KBZ2JN01FzbDkbzw%40mail.gmail.com.
Re: [Trac] Re: Trac 1.0.19 Released
On 2020-01-07 11:04, Roger Oberholtzer wrote: > Perhaps the Plugins that only work with Python 2 should be moved to a > depreciated location? That might make it easier to see which plugins > are effected by a move to Python 3. As a side note: In Debian we are in the process of remving Trac and all packaged plugins as part of the "py2removal" process. We would like to reintroduce the Python-3-based Trac again, when it is ready, of course. For the plugins, it might make sense to mark '''all''' of them as deprecated and only move back one by one, that are really tested against Python-3-based Trac (with no formal definition of "test" here). Are there plugins, that are not affected at all by the move from Python 2 to 3? I doubt that. -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/20200108142705.GA475552%40fama.
Re: [Trac] Re: Trac 1.0.19 Released
On Wed, Jan 8, 2020 at 8:02 AM Steffen Hoffmann wrote: > >Perhaps the Plugins that only work with Python 2 should be moved to a > >depreciated location? That might make it easier to see which plugins > >are effected by a move to Python 3. > > Why do that much extra effort? > > As we did with Trac that had other major, disruptive code changes before, we > can just flag/tag hacks with „trac1.6“ or more explicitely „python3“ as coded > for Python 3. I'm sure that you are correct. I just feel that the actual working support listed for plugins is always a bit iffy at best. One has to install and see what happens. I'm okay with that. I guess there are three (at least) things a plugin needs to be tested for: * Version of Trac * Version of Python * Genshi or whatever What does being Trac 1.4 compatible really mean? Must it also support Python 3? Or are these independent? -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CANkOqwMBHU7K%3DoeiDhmA53ej2UypFE02o-_u3YbhsBnM%3DTOMRA%40mail.gmail.com.
Re: [Trac] Re: Trac 1.0.19 Released
Am 7. Januar 2020 11:04:02 MEZ schrieb Roger Oberholtzer : >On Mon, Jan 6, 2020 at 5:23 PM M M wrote: >> >> What is the point of patching ancient versions? Why not just declare >1.0.x and 1.2.x end of life and focus on 1.4.x and porting to Python3? > >I think I agree. I am guessing the biggest reason for not just >supporting Python 3 is all the plugins that will no longer be usable. >It's not just Trac itself. > >Perhaps the Plugins that only work with Python 2 should be moved to a >depreciated location? That might make it easier to see which plugins >are effected by a move to Python 3. Why do that much extra effort? As we did with Trac that had other major, disruptive code changes before, we can just flag/tag hacks with „trac1.6“ or more explicitely „python3“ as coded for Python 3. Mit freundlichem Gruß Steffen Hoffmann -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/0A21EFF6-664C-411C-A078-0C5C0AC73DB5%40web.de.
Re: [Trac] Re: Trac 1.0.19 Released
On Mon, Jan 6, 2020 at 5:23 PM M M wrote: > > What is the point of patching ancient versions? Why not just declare 1.0.x > and 1.2.x end of life and focus on 1.4.x and porting to Python3? I think I agree. I am guessing the biggest reason for not just supporting Python 3 is all the plugins that will no longer be usable. It's not just Trac itself. Perhaps the Plugins that only work with Python 2 should be moved to a depreciated location? That might make it easier to see which plugins are effected by a move to Python 3. -- Roger Oberholtzer -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/CANkOqwPey4dd_4qWSYkpB%2BRD6o9AeiD7dJ7NpvSCDDcZb9Z_UA%40mail.gmail.com.
[Trac] Re: Trac 1.0.19 Released
What is the point of patching ancient versions? Why not just declare 1.0.x and 1.2.x end of life and focus on 1.4.x and porting to Python3? On Monday, October 14, 2019 at 9:00:39 PM UTC-4, RjOllos wrote: > > Trac 1.0.19, the latest maintenance release for the older stable branch, > is available. > > You will find this release at the usual places: > > https://trac.edgewall.org/wiki/TracDownload#PreviousStableRelease > > You can find the detailed release notes for 1.0.19 on the following > pages: > https://trac.edgewall.org/wiki/1.0/TracChangeLog > https://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.0#MaintenanceReleases > > Now to the packages themselves: > > URLs: > > https://download.edgewall.org/trac/Trac-1.0.19.tar.gz > https://download.edgewall.org/trac/Trac-1.0.19-py2-none-any.whl > https://download.edgewall.org/trac/Trac-1.0.19.win32.exe > https://download.edgewall.org/trac/Trac-1.0.19.win-amd64.exe > > MD5 sums: > > a2f7d22657ef09df6a7117c8b7474d69 Trac-1.0.19.tar.gz > 13d2e3885c46445ac2044aecf489d3c7 Trac-1.0.19-py2-none-any.whl > 20422a1f977dd0c4b799383cab52d0f7 Trac-1.0.19.win32.exe > 0d61b5612ada6fc6bcce4db1f88007bf Trac-1.0.19.win-amd64.exe > > SHA256 sums: > > 026cf713f9e20af9b487e2f8915399a061694e340f7ea4492552ac7c2f48ed13 > Trac-1.0.19.tar.gz > badbc390a2c77a767ed0ceda3235760762ec7e7fdde56d149332b0af273560ef > Trac-1.0.19-py2-none-any.whl > e65b59ff1010122a71ffc972786cdf9f9c09d93f9d7fa9c5350fff951e28e701 > Trac-1.0.19.win32.exe > 7e5e7815ef4b4cf39a1da779dbb185d125f158f871def909237fe6c6e75652f2 > Trac-1.0.19.win-amd64.exe > > Acknowledgements > > > Many thanks to the growing number of people who have, and continue to, > support the project. Also our thanks to all people providing feedback > and bug reports that helps us make Trac better, easier to use and > more effective. Without your invaluable help, Trac would not evolve. > Thank you all. > > Finally, we hope that Trac will be useful to like-minded programmers > around the world, and that this release will be an improvement over > the last version. > > Please let us know. > > /The Trac Team https://trac.edgewall.org/ > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/trac-users/fbe32670-709c-4dc8-bf45-bbff42051ce8%40googlegroups.com.
