Menu
▾
▴
gramps-devel — Gramps developers list
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(35) |
Jun
(11) |
Jul
(41) |
Aug
(96) |
Sep
(29) |
Oct
(44) |
Nov
(70) |
Dec
(61) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2002 |
Jan
(126) |
Feb
(31) |
Mar
(64) |
Apr
(84) |
May
(57) |
Jun
(56) |
Jul
(20) |
Aug
(23) |
Sep
(31) |
Oct
(19) |
Nov
(60) |
Dec
(34) |
| 2003 |
Jan
(30) |
Feb
(61) |
Mar
(32) |
Apr
(30) |
May
(78) |
Jun
(55) |
Jul
(111) |
Aug
(108) |
Sep
(104) |
Oct
(98) |
Nov
(92) |
Dec
(73) |
| 2004 |
Jan
(71) |
Feb
(70) |
Mar
(68) |
Apr
(40) |
May
(118) |
Jun
(51) |
Jul
(71) |
Aug
(251) |
Sep
(77) |
Oct
(155) |
Nov
(74) |
Dec
(57) |
| 2005 |
Jan
(183) |
Feb
(94) |
Mar
(170) |
Apr
(242) |
May
(233) |
Jun
(42) |
Jul
(69) |
Aug
(70) |
Sep
(99) |
Oct
(60) |
Nov
(65) |
Dec
(210) |
| 2006 |
Jan
(169) |
Feb
(99) |
Mar
(31) |
Apr
(179) |
May
(142) |
Jun
(72) |
Jul
(131) |
Aug
(98) |
Sep
(110) |
Oct
(189) |
Nov
(262) |
Dec
(207) |
| 2007 |
Jan
(376) |
Feb
(255) |
Mar
(168) |
Apr
(174) |
May
(167) |
Jun
(192) |
Jul
(197) |
Aug
(171) |
Sep
(307) |
Oct
(572) |
Nov
(454) |
Dec
(471) |
| 2008 |
Jan
(707) |
Feb
(365) |
Mar
(464) |
Apr
(410) |
May
(251) |
Jun
(142) |
Jul
(112) |
Aug
(143) |
Sep
(94) |
Oct
(280) |
Nov
(337) |
Dec
(232) |
| 2009 |
Jan
(508) |
Feb
(491) |
Mar
(363) |
Apr
(280) |
May
(186) |
Jun
(250) |
Jul
(231) |
Aug
(487) |
Sep
(189) |
Oct
(344) |
Nov
(456) |
Dec
(439) |
| 2010 |
Jan
(514) |
Feb
(725) |
Mar
(591) |
Apr
(256) |
May
(209) |
Jun
(75) |
Jul
(118) |
Aug
(248) |
Sep
(230) |
Oct
(393) |
Nov
(368) |
Dec
(276) |
| 2011 |
Jan
(457) |
Feb
(308) |
Mar
(358) |
Apr
(277) |
May
(333) |
Jun
(320) |
Jul
(198) |
Aug
(186) |
Sep
(87) |
Oct
(238) |
Nov
(123) |
Dec
(129) |
| 2012 |
Jan
(127) |
Feb
(182) |
Mar
(208) |
Apr
(134) |
May
(230) |
Jun
(138) |
Jul
(126) |
Aug
(176) |
Sep
(231) |
Oct
(235) |
Nov
(164) |
Dec
(219) |
| 2013 |
Jan
(316) |
Feb
(371) |
Mar
(393) |
Apr
(165) |
May
(321) |
Jun
(301) |
Jul
(124) |
Aug
(183) |
Sep
(191) |
Oct
(285) |
Nov
(172) |
Dec
(196) |
| 2014 |
Jan
(392) |
Feb
(284) |
Mar
(134) |
Apr
(206) |
May
(123) |
Jun
(115) |
Jul
(41) |
Aug
(157) |
Sep
(122) |
Oct
(124) |
Nov
(63) |
Dec
(56) |
| 2015 |
Jan
(249) |
Feb
(335) |
Mar
(277) |
Apr
(98) |
May
(274) |
Jun
(214) |
Jul
(142) |
Aug
(240) |
Sep
(57) |
Oct
(77) |
Nov
(18) |
Dec
(171) |
| 2016 |
Jan
(217) |
Feb
(167) |
Mar
(62) |
Apr
(180) |
May
(270) |
Jun
(86) |
Jul
(112) |
Aug
(50) |
Sep
(57) |
Oct
(91) |
Nov
(62) |
Dec
(101) |
| 2017 |
Jan
(116) |
Feb
(115) |
Mar
(85) |
Apr
(35) |
May
(54) |
Jun
(123) |
Jul
(65) |
Aug
(35) |
Sep
(103) |
Oct
(28) |
Nov
(21) |
Dec
(7) |
| 2018 |
Jan
(27) |
Feb
(64) |
Mar
(42) |
Apr
(72) |
May
(49) |
Jun
(24) |
Jul
(18) |
Aug
(4) |
Sep
(9) |
Oct
(39) |
Nov
(11) |
Dec
(45) |
| 2019 |
Jan
(35) |
Feb
(24) |
Mar
(28) |
Apr
(38) |
May
(16) |
Jun
(41) |
Jul
|
Aug
(49) |
Sep
(41) |
Oct
(22) |
Nov
(15) |
Dec
(32) |
| 2020 |
Jan
(61) |
Feb
(3) |
Mar
(31) |
Apr
(29) |
May
(38) |
Jun
(16) |
Jul
(26) |
Aug
(87) |
Sep
(12) |
Oct
(4) |
Nov
(14) |
Dec
(5) |
| 2021 |
Jan
(3) |
Feb
(4) |
Mar
(26) |
Apr
(2) |
May
(55) |
Jun
(64) |
Jul
(96) |
Aug
(71) |
Sep
(1) |
Oct
(2) |
Nov
(17) |
Dec
(5) |
| 2022 |
Jan
(23) |
Feb
(22) |
Mar
(9) |
Apr
(7) |
May
(8) |
Jun
(6) |
Jul
(2) |
Aug
|
Sep
(14) |
Oct
(10) |
Nov
(1) |
Dec
(10) |
| 2023 |
Jan
(3) |
Feb
|
Mar
|
Apr
(34) |
May
(14) |
Jun
(25) |
Jul
(10) |
Aug
(13) |
Sep
|
Oct
|
Nov
(2) |
Dec
(7) |
| 2024 |
Jan
(1) |
Feb
(23) |
Mar
(33) |
Apr
(19) |
May
(5) |
Jun
(46) |
Jul
(2) |
Aug
(7) |
Sep
(16) |
Oct
|
Nov
(4) |
Dec
(1) |
| 2025 |
Jan
(102) |
Feb
(32) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Nick H. <ni...@gr...> - 2025-03-19 21:25:49
|
Version 6.0.0, a new major release, has been released on 2025-03-19. Make sure to backup before you upgrade. See: https://www.gramps-project.org/wiki/index.php?title=How_to_make_a_backup *Highlights* _Reports_ The narrative web report has four main improvements: * New indexes for big databases. * Add heatmap. * Improve language and hamburger menus. * Show other roles for an event. Other report changes: * Add gender symbol option to the detailed descendant, detailed ancestral and descendant report. * Add Gramps ID option to Kinship Report. * Tree reports convert images to thumbnails for embedding. This allows cropped rectangles selected in the media references to be displayed. * Report options are now memorised on a per family tree (database) level. _Gramplets_ The following updates have been made: * Improvements to the backlinks (References) gramplets: * Allow an object to be made active from within the backlinks gramplet. * Add a context menu to make “Edit” and “Make Active” more discoverable. * Allow objects in the backlinks gramplets to be dragged to the clipboard. * Add edit capability to the notes gramplets. * Enhanced version of the Filter gramplet. _Selector dialogs_ The selector dialogs have been improved: * A standard search bar has been added to the person selector dialog. It may default to selecting men or women by default, but selecting on other columns is possible. * It is now possible to select multiple media objects in the media selector and gallery tabs. * The media selector has a new path column. _Other changes _ * Improvements to the Probably Alive code. * New rules: “Has Event”, “Has Source” and “Having Note of Type”. * New Gedcom 7.0 event roles: “Father”, Mother", “Parent”, “Child”, “Multiple”, Friend", “Neighbour” and “Officiator”. * Allow web-accessible file references in media objects. * Add a preference option for the selection of the toolbar style. * Enhancements to the help display. This is ongoing though. * Enable Web Connection menu in all list views. _Technical stuff_ These changes are probably less interesting to most people: * Many bug fixes. * Removal of deprecated features. * Adding type hints and static type checking. * Code quality improvements and clean-ups. * Extra unit tests. _Database-related changes_ In layman’s terms, the following changes have been made to the database: * We now store objects in the database in a human-readable format. * Power users can now read the database directly without needing to use python. * Certain operations may be slower, but we don’t think by much. * Refactoring and optimisation of the filters/rules should make these much quicker. * The new storage format will make future maintenance and optimisations easier for the developers. * Bug fixes* _v6.0.0_ * Allow Gramps to continue if an addon rule fails to load. Fixes #13676. _ v6.0.0-rc2_ * Remove check that path exists in the media path unit test. Fixes #13305. * Simplify logic for setting data, config and cache directories. Fixes #13261, #13686. * Migrate data from old the directory structure. Fixes #13300. * Fix nested transaction error in the Test Case Generator tool. Fixes #13680. * Fix schema upgrade errors. Fixes #13674. _v6.0.0-rc1_ * Fix upgrades from bsddb. Fixes #13633, #13652. * Fix bug with surname rules in Quick Views. Fixes #13657. * Provide new editor fallback icons for superscript and subscript. Fixes #13548. * Add extra checks when changing a parent in the family editor. Fixes #13642. * Hide navigation bar selector when only one sidebar plugin is loaded. Fixes #13640. * Fix media manager bug with relative to absolute path conversion. Fixes #13644. * Fix bug removing citation references after deleting a source. Fixes #13639. * Fix citation filter rules that search the source. Fixes #13635. * Fix crash in source/citation selector with an empty filter. Fixes #13634. _ v6.0.0-beta2_ * Narrative web: * Remote media cannot be opened. Fixes #13628. * Fix crash with empty an database. Fixes #13619. * Fix to show tree on print page. Fixes #13614. * Center the progress bar in the main window status bar. Fixes #13630. * Remove BSDDB version and duplicate Gramps version from About dialog. Fixes #13624. * Fix crash during bsddb upgrade. Fixes #13627. * Fix error when upgrading a database from 5.1 to 6.0. Fixes #13622. * Ignore missing remote media in check and repair tool. Fixes #13618. * Fix the match method in the GenericFilter class. Fixes #13606. * Fix error when searching by name in the place selector. Fixes #13605. * Enable <Enter> key press on date fields in sidebar filters. Fixes #13607. * Fix all_people() simple access method to use new data format Fixes #13603. * Translation fixes in probably alive code. Fixes #13604. _v6.0.0-beta1_ * Memorise report options for each database. Fixes #2455. * Add help button to plugin selection dialogs. Issue #13467. * Enhance display_help utility function. Add unit tests. Fixes #13562. * Crash with empty ADDR in narrative web. Fixes #13479. * Display the source icon in the event tab of an editor if the event has either an event citation or event reference citation. Fixes #13401. * Fix AttributeError in editor surname tab. Fixes #13322. * Improve the ProbablyAlive code. Implements #13443. * Skip TestImports if en_US locale is not available on build host. Fixes #13079. * Change layout of places and dates in familylines plugin. Adds symbols and changes format of birth and death events. Implements #7788, #10699. * Add missing tooltips in the Addon Manager Implements #13358. * Add support for ISO 639-3 part 3 standard language code. Fixes #12772. * Use preferred name instead of default name in name editor. Fixes #13256. You can obtain Gramps 6.0.0 from the GitHub release page. https://github.com/gramps-project/gramps/releases/tag/v6.0.0 -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Nick H. <ni...@gr...> - 2025-03-15 21:47:50
|
Version 6.0.0-rc2, an experimental pre-release. Make sure to backup before you upgrade: https://www.gramps-project.org/wiki/index.php?title=How_to_make_a_backup The key word is experimental! It might be unwise to "upgrade" your main/real Gramps family tree into 6.0.0-rc2. In general, we recommend you make a copy of your family tree instead (typically by doing a "gramps XML" export), then try 6.0.0-rc2 on the copy. (You can keep things really separate by using the GRAMPSHOME environmental variable, if you want.) We are interested in your feedback, especially if you discover any bugs or problems which we haven't noticed. 2025-03-15 Version 6.0.0-rc2 Update translations: ca, de_AT, en_GB, eo, id, ko, pt_PT, sk, sq. Add python-cffi to the Windows AIO build script. Remove check that path exists in the media path unit test. Fixes #13305. Simplify logic for setting data, config and cache directories. Fixes #13261, #13686. Migrate data from old the directory structure. Fixes #13300. Fix nested transaction error in the Test Case Generator tool. Fixes #13680. Enable Web Connection menu in all list views. Fix schema upgrade errors. Fixes #13674. Add database upgrade unit tests. Package Gramps-6.0.0-rc1 for macOS. You can obtain Gramps 6.0.0-rc2 from the GitHub release page: https://github.com/gramps-project/gramps/releases/tag/v6.0.0-rc2 |
|
From: Jan S. <jan...@ne...> - 2025-02-17 06:21:16
|
Mantis has a problem that now have struck me twice. When creating a new report, which may take some time, the final send report crasches with a suggestion that the cause may be a timeout and you are suggested to go one step back in the browser. However everything is lost, so you have to start over. Thats very annoying. By the way I just reported 13639 <https://gramps-project.org/bugs/view.php?id=13639> for 6.0.0-beta2 noting that it also exists in 5.2.4. Regards Jan Den 2025-01-01 kl. 18:20, skrev Nick Hall via Gramps-devel: > Devs, > > We last discussed which bug tracker to use back in 2015. > > [Gramps-devel] Move to GitHub > > https://sourceforge.net/p/gramps/mailman/message/33278816/ > > When I suggested using GitHub to track issues there were concerns > raised that resulted in us choosing to continue with Mantis BT instead. > > Recently a couple of developers have asked me to enable GitHub Issues, > so perhaps it's time to revisit this topic. Have your views changed > since our last discussion? > > If we decide to use GitHub Issues, then I think that we should migrate > away from Mantis BT. I agree with Benny's comment back in 2015: "I > would like to use the github issue tracker though, but having two ways > is a no-no, so it should be one or the other.". We could keep Mantis > BT read-only for reference. > > I would welcome your opinions on GitHub Issues, Mantis BT or perhaps > an alternative bug tracker. > > Regards, > > > Nick. > > > > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Nick H. <ni...@gr...> - 2025-02-14 22:58:47
|
Translators, We are currently in a string freeze prior to the 6.0 final release. Translations will only be updated when absolutely necessary. This is your opportunity to ensure that the translation for your language is up to date. I have updated the current template. Translations should be made on Weblate only. The new component to translate addons is still in an experimental phase. Translations in this component are not subject to the string freeze. Initial tests are encouraging and we can now merge your translations back into the individual addons. However, there is still more testing to be done and I would suggest that you don't put too much work into translating the Addons component yet. Thanks for your contributions. Regards, Nick. |
|
From: Steve Y. <st...@yo...> - 2025-02-13 09:14:17
|
It doesn't alter my response, but gramps 6.0.0 Windows AIO is currently using python 3.12.9 [I checked the official 6.0.0-beta2 release] ________________________________ From: John Ralls <jr...@ce...> Sent: 11 February 2025 21:42 To: Nick Hall <ni...@gr...> Cc: Gramps Development List <gra...@li...> Subject: Re: [Gramps-devel] Proposal to increase the minimum python requirements > On Feb 11, 2025, at 06:41, Nick Hall via Gramps-devel <gra...@li...> wrote: > > Devs, > > I think that we should consider raising the minimum python requirement to 3.10 and above on the master branch. > > The reason is that we are starting to get PRs that add type annotations, and 3.10 will allow use of the newer neater typing syntax. > > This is a bit early since our current policy says that we support all versions that have not reached end-of-life, but it may make our lives easier in the long run. It is also possible that 3.9 reaches EOL before the release of Gramps 6.1 anyway. > > It is worth noting that the Windows AIO uses 3.13, the Mac bundle uses 3.11 and most modern Linux distributions use 3.10 or above. Users of older Linux distributions can always use Flatpak. With our previous policy we would have probably changed to 3.10 on the EOL of Ubuntu 20.04 in April. > > As usual, let me know your thoughts. +1. Python 3.9 ends support in October: https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdevguide.python.org%2Fversions%2F&data=05%7C02%7C%7C3cadc6fc9d164252460608dd4ae52a27%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638749070302464591%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=0EFmYUFitwVm%2FTJ15bk%2FKcLsSmgYXSPGrBpaY7sp7LI%3D&reserved=0<https://devguide.python.org/versions/> I’ll be doing my annual version bump soon and as will bump python as high as jhbuild will allow (https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgitlab.gnome.org%2FGNOME%2Fjhbuild%2F-%2Fissues%2F291&data=05%7C02%7C%7C3cadc6fc9d164252460608dd4ae52a27%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638749070302484201%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=5MFE7AK%2FFp0tSDLrRWJqlkMcCcvb5J9wu8xv0N63R4I%3D&reserved=0<https://gitlab.gnome.org/GNOME/jhbuild/-/issues/291>). Regards, John Ralls -------------- next part -------------- An HTML attachment was scrubbed... _______________________________________________ Gramps-devel mailing list Gra...@li... https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.sourceforge.net%2Flists%2Flistinfo%2Fgramps-devel&data=05%7C02%7C%7C3cadc6fc9d164252460608dd4ae52a27%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638749070302498077%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=3q5vU7GP%2BbDnMXK2BC7PWvYYItZRVw0llyP5C5IK%2FSQ%3D&reserved=0<https://lists.sourceforge.net/lists/listinfo/gramps-devel> -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Nick H. <ni...@gr...> - 2025-02-13 00:30:23
|
Version 6.0.0-beta2, an experimental pre-release. Make sure to backup before you upgrade: https://www.gramps-project.org/wiki/index.php?title=How_to_make_a_backup The key word is experimental! It might be unwise to "upgrade" your main/real Gramps family tree into 6.0.0-beta2. In general, we recommend you make a copy of your family tree instead (typically by doing a "gramps XML" export), then try 6.0.0-beta2 on the copy. (You can keep things really separate by using the GRAMPSHOME environmental variable, if you want.) We are interested in your feedback, especially if you discover any bugs or problems which we haven't noticed. 2025-02-12 Version 6.0.0-beta2 * Update translations: cs, de, de_AT, fi, he, hr, hu, is, it, nl, pl, pt_PT, sk, sv. * Narrative web: * Add remote media to thumbnail index. * Remote media cannot be opened. Fixes #13628. * Fix crash with empty an database. Fixes #13619. * Fix to show tree on print page. Fixes #13614. * Correctly handle Event == None. * Windows AIO: * Set appbuild correctly. * Add a build-number input to the workflow. * Remove the "-- a new maintenance release" branding from the installer. * Mac: * Remove obsolete gtkspell3 from bundlefile. We're using gspell now. * Package Gramps 6.0.0-beta1 for macOS. * Center the progress bar in the main window status bar. Fixes #13630. * Fix bug in generic filter (swapped lines). * Fix the program name in the About dialog. * Remove BSDDB version and duplicate Gramps version from About dialog. Fixes #13624. * Rename "Help" button to "Wiki" in plugins dialog. Fixes #13625. * Change the progress bar vertical alignment and padding. Fixes #13623. * Import annotations in files using type hints. * Specify the `obj_class` when calling `data_to_object.` * Fix crash during bsddb upgrade. Fixes #13627. * Fix error when upgrading a database from 5.1 to 6.0. Fixes #13622. * Ignore missing remote media in check and repair tool. Fixes #13618. * Don't try to run `get_git_version` in release versions. * Correct the parameter type hints to accept <object> | None. * Private proxy fixes. * Fixed an iter that bypasses proxy. * Fix modifiers in Hungarian date handler. * Added orjson, and 'all' to the setup script. * Updated the README (bsddb3 made optional, removed sqlite3). * Fix the match method in the GenericFilter class. Fixes #13606. * Replace unittest `assertEquals` by `assertEqual`. * Fix type annotation syntax for Python 3.9. * Fix error when searching by name in the place selector. Fixes #13605. * Enable <Enter> key press on date fields in sidebar filters. Fixes #13607. * Fix all_people() simple access method to use new data format Fixes #13603. * Translation fixes in probably alive code. Fixes #13604. * Update CI workflow to run on the gramps60 branch. You can obtain Gramps 6.0.0-beta2 from the GitHub release page: https://github.com/gramps-project/gramps/releases/tag/v6.0.0-beta2 |
|
From: Jan S. <jan...@ne...> - 2025-02-12 08:25:45
|
I got no reaction on this, so I reported it, see https://gramps-project.org/bugs/view.php?id=13628. BR Jan Den 2025-02-09 kl. 21:55, skrev Jan Skarvall: > I forgot to mention that web accessed media is marked as deleted or > moved in the narrative web report. -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: John R. <jr...@ce...> - 2025-02-11 21:42:53
|
> On Feb 11, 2025, at 06:41, Nick Hall via Gramps-devel <gra...@li...> wrote: > > Devs, > > I think that we should consider raising the minimum python requirement to 3.10 and above on the master branch. > > The reason is that we are starting to get PRs that add type annotations, and 3.10 will allow use of the newer neater typing syntax. > > This is a bit early since our current policy says that we support all versions that have not reached end-of-life, but it may make our lives easier in the long run. It is also possible that 3.9 reaches EOL before the release of Gramps 6.1 anyway. > > It is worth noting that the Windows AIO uses 3.13, the Mac bundle uses 3.11 and most modern Linux distributions use 3.10 or above. Users of older Linux distributions can always use Flatpak. With our previous policy we would have probably changed to 3.10 on the EOL of Ubuntu 20.04 in April. > > As usual, let me know your thoughts. +1. Python 3.9 ends support in October: https://devguide.python.org/versions/ I’ll be doing my annual version bump soon and as will bump python as high as jhbuild will allow (https://gitlab.gnome.org/GNOME/jhbuild/-/issues/291). Regards, John Ralls -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Nick H. <ni...@gr...> - 2025-02-11 14:41:14
|
Devs, I think that we should consider raising the minimum python requirement to 3.10 and above on the master branch. The reason is that we are starting to get PRs that add type annotations, and 3.10 will allow use of the newer neater typing syntax. This is a bit early since our current policy says that we support all versions that have not reached end-of-life, but it may make our lives easier in the long run. It is also possible that 3.9 reaches EOL before the release of Gramps 6.1 anyway. It is worth noting that the Windows AIO uses 3.13, the Mac bundle uses 3.11 and most modern Linux distributions use 3.10 or above. Users of older Linux distributions can always use Flatpak. With our previous policy we would have probably changed to 3.10 on the EOL of Ubuntu 20.04 in April. As usual, let me know your thoughts. Regards, Nick. |
|
From: Doug B. <dou...@gm...> - 2025-02-10 19:34:40
|
Thanks for reporting and the sample database! Made it super easy to see issue and fix. https://github.com/gramps-project/gramps/pull/1953 On Mon, Feb 10, 2025 at 1:58 PM Nick Hall via Gramps-devel < gra...@li...> wrote: > On 10/02/2025 08:17, Jan Skarvall wrote: > > Upgrade of the attached small database makes Gramps 6.0.0-beta1_3 > complain > > > I have created bug report #13622 for you with your attachment. > > https://gramps-project.org/bugs/view.php?id=13622 > > > > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Nick H. <ni...@gr...> - 2025-02-10 18:57:22
|
On 10/02/2025 08:17, Jan Skarvall wrote: > Upgrade of the attached small database makes Gramps 6.0.0-beta1_3 complain I have created bug report #13622 for you with your attachment. https://gramps-project.org/bugs/view.php?id=13622 |
|
From: Jan S. <jan...@ne...> - 2025-02-10 08:17:39
|
Upgrade of the attached small database makes Gramps 6.0.0-beta1_3 complain:
46980: ERROR: dbloader.py: line 107: tuple indices must be integers
or slices, not str
Traceback (most recent call last):
File "C:\Program Files\GrampsAIO64-6.0.0\gramps\gui\dbloader.py",
line 198, in read_file
db.load(
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\gen\db\generic.py", line 803, in load
self._gramps_upgrade(dbversion, directory, callback)
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\gen\db\generic.py", line 2759, in
_gramps_upgrade
gramps_upgrade_20(self)
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\gen\db\upgrade.py", line 183, in
gramps_upgrade_20
self._commit_raw(new_person, PERSON_KEY)
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\plugins\db\dbapi\dbapi.py", line 710,
in _commit_raw
handle = data["handle"]
~~~~^^^^^^^^^^
TypeError: tuple indices must be integers or slices, not str
I believe it was created with gramps 5.1.5 but I am not sure.
I just installed gramps 5.2.4 which successfully upgraded the database.
The resulting database upgraded fine with Gramps 6.0.0-beta1_3.
Den 2025-02-05 kl. 18:25, skrev Jan Skarvall:
> Other problems I already noticed are failure to upgrade a tree in the
> database, errors when generating narrative web report, ...
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 6093ab63.tar
Type: application/x-tar
Size: 215040 bytes
Desc: not available
|
|
From: H G. <hg...@ya...> - 2025-02-09 21:23:17
|
On 2/9/2025 2:40 PM, John Ralls wrote: > > Thanks for the heads-up, but please copy gramps-devel on emails like this so that everybody can see them. > > The report is actually about Gramps 5.2.4. ... > I’ve made a PR [1] on maintenance/gramps60 Noted, and thanks for the PR. -- Himanshu (@codefarmer) |
|
From: Jan S. <jan...@ne...> - 2025-02-09 20:55:32
|
I forgot to mention that web accessed media is marked as deleted or
moved in the narrative web report.
> I have written a thumbnailer for remote media, although it isn't
> publicly available yet. I can let you have a copy to test. It uses a
> locally installed web browser in headless mode to thumbnail any
> webpage. The "application/http" is used to identify that a web
> thumbnailer should be used if available.
>
I'm interested. I have a problem though to debug gramps. When starting
gramps I get:
WARNING:root:The orjson package is needed to start Gramps.
Gramps will terminate now.
2025-02-09 21:42:24.182: WARNING: grampsapp.py: line 225: The orjson
package is needed to start Gramps.
Gramps will terminate now.
I'm struggling to install orjson, but there is no python3-orjson package
for Debian 12 (bookworm), which I am using. Tried:
$ pip3 install orjson
error: externally-managed-environment
:
:
You can override this, at the risk of breaking your Python
installation or OS, by passing --break-system-packages.
I have not (yet) dared to use the --break-system-packages option.
>
> Regards,
>
>
> Nick.
>
BR
Jan
-------------- next part --------------
An HTML attachment was scrubbed...
|
|
From: John R. <jr...@ce...> - 2025-02-09 19:41:16
|
Himanishu, Thanks for the heads-up, but please copy gramps-devel on emails like this so that everybody can see them. The report is actually about Gramps 5.2.4. It’s kind of surprising that this hasn’t come up before as the code to run git at startup (https://github.com/gramps-project/gramps/blob/0f8d4ecd429431b4df64910962f8764af9ff1766/gramps/gen/const.py#L174) has been in Gramps for 14 years and macOS has been offering to install command line tools for at least 10. I’ve made a PR [1] on maintenance/gramps60 because I’m under the impression that 5.2.4 was the last gramps52 release. If that’s mistaken it’s not a big deal to change the PR. Regards, John Ralls > On Feb 9, 2025, at 10:37 AM, H Gohel <hg...@ya...> wrote: > > Hi John, > > There's a MacOS user who posted an issue with Gramps 6.0.0 beta 1 on the Discourse forum. I believe you're not on there, so I wanted to give you a heads up: > > https://gramps.discourse.group/t/mac-command-line-tool-for-git/6965 > > Thanks, > -- > Himanshu (@codefarmer) > |
|
From: Nick H. <ni...@gr...> - 2025-02-09 19:01:00
|
On 09/02/2025 15:37, Jan Skarvall wrote: > I tried to create > some web accessible media objects. It is possible to do that but it > is a bit awkward. It is not as simple as currently adding an > Internet link to e.g. a person. When trying to add a web accessible > media object to a person, the media reference editor pops up, and on > top of it the file browser/choser pops up. Yes, it is a bit awkward, but I didn't want to make selecting local media more difficult. We can always add an extra button and dialog in the future if people find this feature useful. > I noted that any web accessible media gets the media type > application/http. That is the case even if the URL points directly > to e.g. a JPG or PDF file. That differs from media types of local > files. I would suggest to try to find out the media types of the > files that the URL points to e.g. using something like what is > described in Python: How to get the Content-Type of an URL? > <https://stackoverflow.com/questions/12474406/python-how-to-get-the-content-type-of-an-url> > > That would likely allow the usage of thumbnails for web accessed > images. I have written a thumbnailer for remote media, although it isn't publicly available yet. I can let you have a copy to test. It uses a locally installed web browser in headless mode to thumbnail any webpage. The "application/http" is used to identify that a web thumbnailer should be used if available. > I know that there are concerns about entering references to the web > in a gramps tree, references that may become stale. So I checked how > gramps reacts to a change of the name of a local file that is > referred by the gramps tree. We never check to see if local media have been updated, so I don't do so with remote media either. > I went on running the check and repair database tool. It found both > the missing file and the broken URL. However it also complained > about a valid URL saying media object could not be found. This is probably a real bug. I have create a bug report: https://gramps-project.org/bugs/view.php?id=13618 > As I noted in PR1447 > <https://github.com/gramps-project/gramps/pull/1447#issuecomment-1666452699> > > I think that the image crop stuff could be hidden for media types > other than image/xxx. We could consider that for the future. Regards, Nick. |
|
From: Jan S. <jan...@ne...> - 2025-02-09 15:38:13
|
Hi again
I expected that reporting things I discovered in 6.0.0 beta in Mantis
would clearly indicate that the "bug" was discovered in that release.
I could not find a way to do that which would make me certain that those
working on the beta release would be notified.
So I instead summarize my findings related to web accessible media in
this mail. What I so far have found is based on installing
GrampsAIO-6.0.0-beta1-3_win64.exe on a laptop running Windows 10. I
started out with GrampsAIO-6.0.0-beta1-1_win64.exe that run into
problems with libgcc_s_seh-1.dll which a reported. I never got a
notification that it was fixed. It was by "accident" I saw that there
was newer installation files, so I
tried GrampsAIO-6.0.0-beta1-3_win64.exe which does not have that
problem. So, I lost some time on not knowing.
In summary i found the following problems:
1. I get numerous crashes that are not related to web accessible media.
They all occur when trying to create a narrative web report and are
all caused by me starting out with a rather empty family tree. The
first example output is:
2025-02-05 14:58:42.905: ERROR: _reportdialog.py: line 801:
Failed to run report.
Traceback (most recent call last):
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\gui\plug\report\_reportdialog.py",
line 760, in report
my_report.write_report()
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\plugins\webreport\narrativeweb.py",
line 561, in write_report
self.tab["Family"].display_pages(the_lang, the_title)
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\plugins\webreport\family.py", line
128, in display_pages
self.familylistpage(
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\plugins\webreport\family.py", line
438, in familylistpage
max_rows = max_letter_rows[bletter]
^^^^^^^
UnboundLocalError: cannot access local variable 'bletter' where
it is not associated with a value
At that point I added a family with the single person I had, which
made the problem move to this:
2025-02-05 15:02:23.508: ERROR: _reportdialog.py: line 801:
Failed to run report.
Traceback (most recent call last):
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\gui\plug\report\_reportdialog.py",
line 760, in report
my_report.write_report()
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\plugins\webreport\narrativeweb.py",
line 569, in write_report
self.tab["Place"].display_pages(the_lang, the_title)
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\plugins\webreport\place.py", line
183, in display_pages
self.placelistpage(self.report, the_lang, the_title)
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\plugins\webreport\place.py", line
449, in placelistpage
max_rows = max_letter_rows[bletter]
^^^^^^^
UnboundLocalError: cannot access local variable 'bletter' where
it is not associated with a value
and so on, e.g. for no sources:
:
:
File "C:\Program
Files\GrampsAIO64-6.0.0\gramps\plugins\webreport\source.py", line
322, in sourcelistpage
max_rows = max_letter_rows[bletter]
^^^^^^^
UnboundLocalError: cannot access local variable 'bletter' where
it is not associated with a value
2. After having added things to the tree that finally allowed a
successful narrative web report to be created, I tried to create
some web accessible media objects. It is possible to do that but it
is a bit awkward. It is not as simple as currently adding an
Internet link to e.g. a person. When trying to add a web accessible
media object to a person, the media reference editor pops up, and on
top of it the file browser/choser pops up. You have to close (or
cancel) that file browser/choser, then expand the "Detailed
information" part of the media reference editor to be able to enter
the URL as the search path. Doing it directly, i.e. not via a
person, the file browser/choser pops up on top of the media editor
and again must be closed before entering the URL.
I would suggest to handle local and remote media as far as possible
in the same way. My suggestion is to skip the automatic opening of
the file browser/choser and possibly, but not necessarily, add a
button to open something like the existing Internet Address editor
(which has a button to open the URL in the standard browser) beside
the already existing button to open the file browser/choser:
3. I noted that any web accessible media gets the media type
application/http. That is the case even if the URL points directly
to e.g. a JPG or PDF file. That differs from media types of local
files. I would suggest to try to find out the media types of the
files that the URL points to e.g. using something like what is
described in Python: How to get the Content-Type of an URL?
<https://stackoverflow.com/questions/12474406/python-how-to-get-the-content-type-of-an-url>
That would likely allow the usage of thumbnails for web accessed
images. A local file, e.g. named index.html containing HTML code
actually gets the media type text/html when added as media to
gramps. That would be the common case for me, having source objects
containing web based media like
https://sok.riksarkivet.se/bildvisning/00039503_00012. (Some pages
on that site requires you to open a (free) account, so you may be
required to login to see what the URL points to. Both the login page
and the actual page would have media type text/html.)
4. I know that there are concerns about entering references to the web
in a gramps tree, references that may become stale. So I checked how
gramps reacts to a change of the name of a local file that is
referred by the gramps tree. No warning was issued for the following
three cases. Same goes after adding web accessed media with broken
URL's. I'm not sure if warnings should be issued. The 3 tests are:
1. Creating a narrative web report does not warn about the missing
local file. Trying to show the file in the report tells that it
is moved or deleted.
2. Creating a backup of the tree does not warn about the missing
local file.
3. Exporting the tree as XML including media does not warn about
the missing local file. The file reference is there, but the
file is missing.
5. I went on running the check and repair database tool. It found both
the missing file and the broken URL. However it also complained
about a valid URL saying media object could not be found.
6. As I noted in PR1447
<https://github.com/gramps-project/gramps/pull/1447#issuecomment-1666452699>
I think that the image crop stuff could be hidden for media types
other than image/xxx.
Best regards
Jan
Den 2025-02-05 kl. 18:34, skrev Doug Blank:
>
> On Wed, Feb 5, 2025 at 12:26 PM Jan Skarvall <jan...@ne...>
> wrote:
>
> [snip]
>
> Other problems I already noticed are failure to upgrade a tree in the
> database, errors when generating narrative web report, ...
>
>
> Thanks for testing! Please report all issues (especially these two)
> with instructions on the details, and how to replicate, if possible.
>
> Instructions for reporting issues is here:
> https://www.gramps-project.org/wiki/index.php/Using_the_bug_tracker
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BhMVyEeBvlCPBSJs.png
Type: image/png
Size: 31074 bytes
Desc: not available
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mxgzcs1EDTlB5cBZ.png
Type: image/png
Size: 14554 bytes
Desc: not available
|
|
From: Nick H. <ni...@gr...> - 2025-02-09 00:20:28
|
On 03/01/2025 18:38, Nick Hall via Gramps-devel wrote:
> I am considering translating the addons using Weblate.
>
> The obvious way would be to create a new component for each addon.
> This would involve some repetitive work to set up and also ongoing
> maintenance when addons are added or removed. Switching between
> branches may also be awkward.
>
> An alternative is to combine all the template.pot files into a single
> addons.pot file using msgcat. The translations can then be extracted
> again using msgcomm. It works quite well, but we lose the copyright
> details for the individual addons. The copyright statements would be
> aggregated and maintained in the combined addons.pot file.
I have created an experimental Addons component in Weblate.
It uses a new "po" directory in the addons-source repository. This
contains an addons.pot file which is an aggregation of all the
template.pot files and {lang}.po files which are an aggregation of all
the {lang}-local.po files. I have excluded string from addons.pot that
are already in the main gramps.pot file.
I have out the following warning for translators: "The Addons component
contains aggregated translations for every addon. At this stage it is
experimental. Please only translate a few strings so we can check that
it is working correctly."
Please have a look at the component in Weblate:
https://hosted.weblate.org/projects/gramps-project/addons/
Any checks and feedback would be appreciated. I can remove the
component if people think that this is a bad idea.
I'll publish the aggregations and extraction scripts shortly. They need
tidying up.
Regards,
Nick.
|
|
From: David S. <st...@pr...> - 2025-02-05 18:41:44
|
> Good point. But we should restructure those a bit. Some can be removed (bsddb3), but the idea that: > pip install gramps["image"] > > is more useful than: > pip install pillow The usefulness of the "image" extra is debatable, but I think each of the optional dependencies should appear in one of the extras and I don't know where else it would fit. > Seems make it overly complicated. It would be better perhaps to have a: > pip install gramps["everything"] The convention is usually to have an "all" (not "everything") extra containing all optionals. But I think what we should certainly keep is the separation of GUI extra dependencies. (Ironically, currently these are still required by Web API though, as the separation is not perfect). -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: <Emy...@ya...> - 2025-02-05 17:36:12
|
Our MantisBT has been configured to restrict Edits to certain permission levels. I believe that this is because MantisBT doesn't have an EFFECTIVE system for notifying followers of an issue of what edit occurred in the free-form text fields. It only has effective notifications of new comments... or changes to the structured data fields. Those, it identifies well. MantisBT can tell followers that an Edit occurred, but it takes too much effort for followers to compare and contrast. I do wish it allowed changes in the 1st 30 minutes so we could do a fast commit, then fix typos and lightly refine. (That security token timeout in MantisBT makes a person hasty.) On Wed, Feb 5, 2025 at 10:43 AM, Thierry Vignaud<thi...@gm...> wrote: Le mer. 5 févr. 2025 à 15:09, Thierry Vignaud <thi...@gm...> a écrit : > Le mar. 4 févr. 2025 à 23:11, Nick Hall via Gramps-devel < > gra...@li...> a écrit : > >> Version 6.0.0-beta1, an experimental pre-release. >> >> Make sure to backup before you upgrade: >> >> > Looks like OK for now. > Packaging orjson was painful though due to all the rust packages to create > as deps. > Another related beta1 bug : https://gramps-project.org/bugs/view.php?id=13606 display is corrupted or places disappear from search view after altering the "enclosed by" field Remembering the git issues vs mantis bug tracker, it's painful one cannot set the version or the reproducibility field after filling a bug. Why cannot we alter the details of a bug we filled ? All other bug trackers enable you to do that… -------------- next part -------------- An HTML attachment was scrubbed... _______________________________________________ Gramps-devel mailing list Gra...@li... https://lists.sourceforge.net/lists/listinfo/gramps-devel -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Doug B. <dou...@gm...> - 2025-02-05 17:34:33
|
On Wed, Feb 5, 2025 at 12:26 PM Jan Skarvall <jan...@ne...> wrote: [snip] Other problems I already noticed are failure to upgrade a tree in the > database, errors when generating narrative web report, ... > Thanks for testing! Please report all issues (especially these two) with instructions on the details, and how to replicate, if possible. Instructions for reporting issues is here: https://www.gramps-project.org/wiki/index.php/Using_the_bug_tracker -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Doug B. <dou...@gm...> - 2025-02-05 17:30:37
|
On Wed, Feb 5, 2025 at 12:10 PM David Straub via Gramps-devel < gra...@li...> wrote: > > But if just adding the install_requires works, then we should do that. > We can also add some other packages for easy use, like pillow, pycairo, > PyGObject, and imagesize (maybe others). > > No, they are in extras_require as they are optional: > https://github.com/gramps-project/gramps/blob/master/setup.py#L453-L459 > > Good point. But we should restructure those a bit. Some can be removed (bsddb3), but the idea that: pip install gramps["image"] is more useful than: pip install pillow Seems make it overly complicated. It would be better perhaps to have a: pip install gramps["everything"] rather a few with single packages in them. Many (all?) of these are small little packages anyway. -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Jan S. <jan...@ne...> - 2025-02-05 17:26:05
|
Hi all
I was very happy to see that "Allow web-accessible file references in
media objects." is merged into 6.0.0-beta1 as, for me, it is important
to allow that source objects can refer to the web. So I set out to have
a closer look at the 6.0.0-beta1 release. I started with installing
GrampsAIO-6.0.0-beta1-1_win64.exe on a laptop I have which runs Windows
10. It installs fine and I can do some simple testing that already
revealed some problems that I want to report. I am not sure about how to
report those problems though, so I start with reporting one of the first
issues I have stumbled on in this mail:
Right after successful installation I can select (in a check box) to
start gramps right away. Then it runs fine. If I then close gramps and
tries to start it again i get this pop-up:
It is in swedish but says that libgcc_s_seh-1.dll can not be found
and suggests to reinstall the program, i.e. gramps.
The same thing happens if I chose not to run gramps right after
successful installation, and then tries to start gramps.
As soon as I know how to report other issues related to web-accessible
file references in media objects I will go on with that.
Other problems I already noticed are failure to upgrade a tree in the
database, errors when generating narrative web report, ...
Best regards
Jan
Den 2025-02-04 kl. 23:10, skrev Nick Hall via Gramps-devel:
> Version 6.0.0-beta1, an experimental pre-release.
>
> Make sure to backup before you upgrade:
>
> https://www.gramps-project.org/wiki/index.php?title=How_to_make_a_backup
>
> The key word is experimental!
>
> It might be unwise to "upgrade" your main/real Gramps family tree into
> 6.0.0-beta1. In general, we recommend you make a copy of your family
> tree instead (typically by doing a "gramps XML" export), then try
> 6.0.0-beta1 on the copy. (You can keep things really separate by using
> the GRAMPSHOME environmental variable, if you want.)
>
> We are interested in your feedback, especially if you discover any
> bugs or problems which we haven't noticed.
>
> 2025-02-04
> Version 6.0.0-beta1
> * Update translations: ar, bg, br, ca, cs, da, de, de_AT, el, en_GB,
> eo, es, fa, fi, fr, ga, gl, he, hr, hu, id, is, it, ja, ko, lt, mk,
> nb, nl, nn, pl, pt_BR, pt_PT, ro, ru, sk, sl, sq, sr, sv, ta, tr, uk,
> vi, zh_CN, zh_HK, zh_TW.
> * Update development status classifier.
> * Update translation template for new release.
> * Fix xgettext format string.
> * Add missing files to `POTFILES.in`.
> * Fix accessing an attribute in a `DataDict`.
> * Add missing future import for annotations.
> * Add type hints to modified functions.
> * Optimise `get_object_from_gramps_id` methods in filter proxy.
> * Refactor, fix, and optimize filters/rules.
> * Add `GrampsID` type hints to `DbGeneric`.
> * Define types for Gramps IDs.
> * Add licence and copyright.
> * Make the orjson package mandatory.
> * Use orjson with a hand-coded encoder/decoder. Assumes orjson is
> installed.
> * Disable pylintrc no-else-return check.
> * Allow web-accessible file references in media objects.
> * Add type hints to the generic database handler.
> * Update Info.plist for Gramps 6.0. The important change is that macOS
> 11.0 is now the minimum required for both Intel and Apple Silicon Macs.
> * Add heatmap to the narrative web report.
> * Memorise report options for each database. Fixes #2455.
> * Add help_url to built-in tools.
> * Add help button to plugin selection dialogs. Issue #13467.
> * Enhance display_help utility function:
> * Allow the webpage to include a section separated by a hash (#)
> character.
> * Allow a webpage starting with http:// or https:// to specify a
> full url.
> * Add unit tests. Fixes #13562.
> * Update minimum python version.
> * Add type hints to latitude and logitude related methods and functions.
> * Use attributes rather than dictionary lookup in the model classes.
> * Crash with empty ADDR in narrative web. Fixes #13479.
> * New indexes for big databases in the narrative web report.
> * Correct the tab name for setting the date format in a Tip of the Day.
> * Remove unnecessary translations.
> * Fixes to probably alive code following reviewer comments.
> * Fix safe mode on Windows Safe mode.
> * Make cleanup optional after an AIO build.
> * Add type information to base selector.
> * Use search bar filters instead of fast filter classes.
> * Search bar filter has precedence.
> * Add the standard search bar to the SelectPerson dialog.
> * Add a preference option for the selection of the toolbar style.
> * Use ngettext when displaying the max probably alive age in years.
> * Rephrase the citation references option in the narrative web report.
> * The example filename in the welcome gramplet should not be translated.
> * The space used as an empty column heading does not need translation.
> * Add a translation context to a couple of name origin types.
> * Use ngettext in probably alive function.
> * Remove unreachable else statement in probably alive code.
> * Fix "alt_names" typo in the place model.
> * Add new place to example database.
> * Fix date modifiers for is.
> * Fix de_AT translation.
> * Change http:// to https:// in Tip of the Day file.
> * Strongly recommend orjson in the README.
> * Add orjson version strings.
> * Add orjson dependency to Windows AIO.
> * Add orjson dependency to Mac bundle.
> * Use orjson, if available.
> * Fix exact search filters in selector dialogs.
> * Allow importing and exporting nicknames to CSV.
> * Replace assert statements with `TestCase` methods in unit tests.
> * Fix python format string related xgettext warnings.
> * Fix narrative web when a person excluded by a proxy is referenced.
> * Recognize event reference citations in editor event tabs.
> * Display the source icon in the event tab of an editor if the event
> has either an event citation or event reference citation. Fixes #13401.
> * Fix AttributeError in editor surname tab. Fixes #13322.
> * Allow multiple selection in the gallery tab in editors.
> * Allow multiple selection in the media selector dialog.
> * Add optional support for multiple selction in selector dialogs.
> * Merge the two different `MultiTreeView` classes.
> * dd path column to the media selector dialog.
> * Remove serialize from changenames.
> * Create `DataDict` from object; Get object with `from_dict()`:
> * Allow construction of a DataDict from an instance.
> * Clean up `DataDict` a bit
> * Return object instance `from_dict()` if it exists.
> * Improve language and hamburger menus in narrative web report:
> * Improve the backlinks (References) gramplets
> * Enhance `ListModel` to handle middle mouse clicks.
> * Allow an object to be made active from within the backlinks gramplet.
> * Add a context menu to make "Edit" and "Make Active" more
> discoverable.
> * Allow objects in the backlinks gramplets to be dragged to the
> clipboard.
> * Display the Date column for all objects which are an instance of
> `DateBase`.
> * Fix exception during Redo operation.
> * Set initial focus in `EditPlaceRef` dialog.
> * Add edit capability to the set of Notes gramplets.
> * Update the gramplet display when a note is updated, added or deleted.
> * Use Ubuntu 22.04 for CI.
> * Add gender symbol option to the detailed descendant report.
> * Add gender symbol option to the detailed ancestral report.
> * Add gender symbol option to the descendant report.
> * Add an option to insert a gender symbol before the person's name.
> * Enable mypy static type checking.
> * Remove trailing whitespace check. This is now performed by black.
> * Fix the spelling of "because" in comments.
> * Refactor `GrampsType` set method to use functools.singledispatchmethod.
> * Convert images in tree reports to thumbnails for embedding.
> * Improve the ProbablyAlive code. Implements #13443.
> * Update bundle for gspell, new enchant.
> * Convert 'Tip of the Day' window to `Gtk.Template`.
> * Add PyPI upload workflow.
> * Change variable name to 'data' for consistency across the code base.
> * Fix error in Fast*Filter.
> * Update `GrampsType` to work with dict objects.
> * Replace deprecated 'warn' method with 'warning'.
> * Replace deprecated makeSuite with TestLoader().loadTestsFromTestCase.
> * Skip TestImports if en_US locale is not available on build host.
> Fixes #13079.
> * Fix unittest for local timezones.
> * Update Debian build to include Ubuntu 24.04.
> * Add new HasEvent and HasSource rules.
> * Translate the filter comment string.
> * Use css error class rather then hardcoding the colour "red".
> * Enhanced version of the Filter gramplet.
> * Add new 'having note of type' rule.
> * Change layout of places and dates in familylines plugin. Adds
> symbols and changes format of birth and death events. Implements
> #7788, #10699.
> * Show other roles for an event in the narrative web report.
> * Harmonize Date Format label capitalization.
> * Add link to Sphinx footer add hotlink to footer for potential
> contributors.
> * Add missing tooltips in the Addon Manager. Implements #13358.
> * Add Gramps ID option to Kinship Report.
> * Allow Gramps to run from an extracted source distribution.
> * Use standard decorator form of defining properties.
> * Replace deprecated Gdk.Color by Gdk.RGBA.
> * Fix deprecation on ElementTree truth testing.
> * Stop displaying Python-sqlite3 version.
> * implify multiple calls to `str.startswith` / `str.endswith`.
> * Remove redundant definition of _has_webpage_extension.
> * Use contextlib to redirect stdout/stderr.
> * Remove deprecated use-action-appearance property.
> * Remove stock items from Glade files.
> * Fix xalign deprecations in Glade files.
> * Fix margin-* deprecations in Glade files.
> * Added 11k serialize tests.
> * Added a dict wrapper that acts like an object.
> * Switch from pickled blobs to JSON data.
> * Store empty date objects instead of null in the JSON schema.
> * Refactor JSON serialization.
> * Make BaseObject the parent class for `Date`, `StyledText` and
> `StyledTextTag.`
> * Add PyPI upload workflow.
> * Some filter rule type related cleanups.
> * Add new role types present in the Gedcom 7.0 specification.
> * Replace deprecated `Gtk[HV]Box` with `GtkBox`.
> * Add support for ISO 639-3 part 3 standard language code. Fixes #12772.
> * Change the output of ADDR tags in the Gedcom export.
> * Use preferred name instead of default name in name editor. Fixes
> #13256.
> * Prevent forwards/backwards when history is locked.
> * Add forwards and backwards navigation using mouse buttons.
> * Pylint cleanups for gen/db/*.py.
> * Some pylint cleanups for gramps/gen/plug/*.py.
> * Pylint cleanups for plugins/db/dbapi/*.py.
> * Pylint cleanups for gen/lib/*.py:
> * Reformat to default 88 columns and factor out `EventBase`.
> * Use of _ is cleaner for unreferenced vars.
> * Allow 0 ancestors/descendants in hourglass graph.
> * Sort AIO prerequisites + remove unneeded.
> * Simplify some Cairo drawing.
> * Remove unused Subversion keyword substitutions.
> * Replace `GtkMenu` with `GioMenu` in DropdownSidebar.
> * Convert navigator from a Notebook to a Stack.
> * Convert navigator menu into a combo box.
> * Fix typo in Navigator action/section id.
> * Remove unused code from Navigator.
> * Replace `GtkMenu` with `GioMenu` in Gramplets bar.
> * Replace `GtkArrow` with `GtkImage` and symbolic icons.
> * Update format of Glade files.
> * Glade files regenerated using 3.40.0.
> * Required Gtk version set to 3.24.
> * Restrict CI workflow to run on a single branch.
> * Update GitHub actions to latest versions.
>
> You can obtain Gramps 6.0.0-beta1 from the GitHub release page:
>
> https://github.com/gramps-project/gramps/releases/tag/v6.0.0-beta1
>
>
>
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dLWsEgMiRevlNElu.png
Type: image/png
Size: 9279 bytes
Desc: not available
|
|
From: David S. <st...@pr...> - 2025-02-05 17:09:42
|
> But if just adding the install_requires works, then we should do that. We can also add some other packages for easy use, like pillow, pycairo, PyGObject, and imagesize (maybe others). No, they are in extras_require as they are optional: https://github.com/gramps-project/gramps/blob/master/setup.py#L453-L459 > -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Doug B. <dou...@gm...> - 2025-02-05 17:06:15
|
On Wed, Feb 5, 2025 at 9:10 AM Nick Hall via Gramps-devel < gra...@li...> wrote: > On 05/02/2025 08:09, David Straub wrote: > > quick question, why is orjson not listed as dependency in setup.py? This > is needed for pip-installability. > > I'm not sure. Doug made a comment in PR #1837 that install_requires was > ignored so he removed it. > > I was wrestling with Gramps bespoke setup.py. It seems that "pip install gramps" should run the build and install step. But if just adding the install_requires works, then we should do that. We can also add some other packages for easy use, like pillow, pycairo, PyGObject, and imagesize (maybe others). BTW, sqlite3 doesn't need to be listed (standard Python now), and bsddb3 can be removed from: https://github.com/gramps-project/gramps/blob/master/README.md -------------- next part -------------- An HTML attachment was scrubbed... |
141 messages has been excluded from this view by a project administrator.
