pywikibot August 2016

pywikibot@lists.wikimedia.org

23 participants
24 discussions

Regex for chemicals
by Bináris 10 Aug '16

10 Aug '16

Hi, does anyone have a good regex for chemical formulae? These samples below were found with \d,\d,\d\S+-\d-\S+ which seems pretty good in not matching falses (every match is OK), but I don't know how many matches are left out. Do you know a better onee without false positives? Template occurrences are not on purpose, I have to find them anywhere. I don't need a perfect one, just a "good enough", because I don't want to colletc them, I just want to exclude from spelling corrections. - |IUPACnév = (6a''R'',9''R'')-''N'',''N''-dietil-7-metil-4,6,6a,7,8,9-hexahidroindol-[4,3-''fg'']kinolin-9-karboxamid - |IUPACnév = 2-(2,4-difluorophenyl)- 1,3-''bis''(1''H''-1,2,4-triazol-1-yl)propan-2-ol - az E- és Z-4,5,9-tritiadodeka-1,6,11-trién - |IUPACnév = ''6-(2-fluorfenil)-2-metil-9-nitro- 2,5-diazabiciklo[5.4.0]undeka- 5,8,10,12-tetraén-3-on'' - |IUPACnév = (8''S'',10''S'')-10-(4-amino-5-hidroxi-6-metil- tetrahidro-2''H''-pirán-2-iloxi) -6,8,11-trihidroxi-8-(2-hidroxiacetil) -1-metoxi-7,8,9,10-tetrahidrotetracén -5,12-dion - |IUPACnév = ''6-(2-chlorophenyl)-9-nitro- 2,5-diazabicyclo[5.4.0]undeca- 5,8,10,12-tetraen-3-one'' - | IUPACnév = (2''R'',4''S'')-''rel''-4-[4-[4-[4-[ [2-(2,4-dichlorophenyl)- 2-(1H-1,2,4-triazol-1-ylmethyl)- 1,3-dioxolan-4- - |IUPACnév = 4-[2-ethoxy-5-(4-ethylpiperazin-1-yl)sulfonyl-phenyl]- 9-methyl-7-propyl- 3,5,6,8-tetrazabicyclo[4.3.0] nona-3,7,9-trien-2-o ne - |IUPACnév = (6''R''-transz)-6-(1,3-benzodioxol-5-il)- 2,3,6,7,12,12a-hexahidro-2-metil-pirazino [1', 2':1,6] pirido[3,4-''b'']indol-1,4-dion - |IUPACnév = (7''S'',9''E'',11''S'',12''R'',13''S'',14''R'',15''R'',16''R'',17''S'',18''S'',19''E'',21''Z'')-2,15,17,27,29-pentahidroxi-11-metoxi-3 ,7,12,14,16,18,22-heptametil-26-{(E)-[(4-metilpiperazin-1-il)imino]metil}-6,23-dioxo-8,30-dioxa-24-azatetraciklo[23.3.1.14,7.05,28</s up>]triakonta-1(28),2,4,9,19,21,25(29),26-oktaén-13-il-acetát - |Szinoníma = 5,6,9,17,19,21-hexahidroxi-23-metoxi-2,4,12,16,18,20,22-heptametil-8-[''N''-(4-metil-1-piperazinil)formimidoil]-2,7-(epoxip entadeka[1,11,13]triénimino)-nafto[2,1-''b'']furán-1,11(2''H'')-dion-21-acetát - |IUPACnév = (''S'')-2-[4-[2-(4-amino-2-oxo-3,5,7-triazabiciklo[4.3.0] nona-3,8,10-trién-9-il)etil] benzoil] aminopentándisav - | IUPACName = 1,17-dihydroxy-10,13-dimethyl-17-[2-(4-methylpiperazin-1-yl)acetyl]-7,8,9,11,12,14,15,16-octahydro-6''H''-cyclopenta[a]phenanthren-3- one - | IUPACNév = 1,1,1-Trichloro-2-methyl-2-propanol - | MásNév = 1,1,1-trichloro-2-methyl-2-propanol, chlorbutol, chloreton, chloretone, chlortran, trichloro-tert-butyl alcohol, 1,1,1-trichloro-tert-bu tyl alcohol, 2-(trichloromethyl)propan-2-ol, 1,1,1-trichloro-2-methyl-2-propanol, tert-Trichlorobutyl alcohol, trichloro-tert-butanol, trichlorisobut - |IUPACnév = ''(RS)''-[4-(4-amino-6,7-dimethoxy- quinazolin-2-yl) piperazin-1-yl]- (2,5-dioxabicyclo[4.4.0] deca-6,8,10-trien-4-yl) methanone - |IUPACnév = 3,5-dihidroxi-7-[6-hidroxi-2-metil-8-(2-metilbutanoiloxi)-1,2,6,7,8,8a-hexahidronaftalén-1-il]-heptánsav - |IUPACnév = 9-nitro-6-fenil-2,5-diazabiciklo[5.4.0]undeka-5,8,10,12-tetraén-3-on - |IUPACName=2-metil-3-[(2''E'')-3,7,11,15-tetrametilhexadec-2-én-1-il]naftokinon - | IUPAC_name = (8''S'',9''S'',10''S'',13''S'',14''S'',17''S'')-17-hidroxi-10, 13,17-trimetil-7,8,9,11,12,14,15,16- oktahidro-6''H''-ciklopent a[a]fenantrén-3-on - | 17916||C.I. Reactive black 1.||Cibacron Black BG||<nowiki>Cobalt,4-[[6-[(4-amino-6-chloro-1,3,5-triazin-2-yl)amino]-1-hydroxy-3-sulfo-2-naphthale nyl]azo]-3-hydroxy-7-nitro-1-naphthalenesulfonicacid complex (9CI)</nowiki> l)azo]-2,7-naphthalenedisulfonic acid complex - | IUPACName = (3β,5''Z'',7''E'')-9,10-secocholesta- 5,7,10(19)-trien-3-ol - | IUPACName = 2,2′-''bisz''-(8-formil-1,6,7-trihidroxi-5-izopropil-3-metilnaftalin) - | IUPACName = 2,5-anhidro-1,4,6-trideoxi-6-(trimetilammónio)-D-''ribo''-hexit - |IUPACnév = (6''R'',7''R'',''Z'')-7-(2-(2-aminothiazol-4-yl)- 2-(methoxyimino)acetamido)-3-((6-hydroxy-2-methyl-5-oxo- 2,5-dihydro-1,2,4 -triazin-3-ylthio)methyl)-8-oxo-5-thia- 1-aza-bicyclo[4.2.0]oct-2-ene-2-carboxylic acid - |IUPACnév = 4,4-difluoro-''N''-{(1''S'')-3-[3-(3-isopropyl-5-methyl-4''H''-1,2,4-triazol-4-yl)- - |IUPACnév = (5-metil-2-oxo-2''H''-1,3-dioxol-4-il)metil-4-(2-hidroxipropán-2-il)-2-propil-1-({4-[2-(2''H''-1,2,3,4-tetrazol-5-il)fenil]fenil}metil )-1''H''-imidazol-5-karboxilát - | IUPACName =7-α-D-Glucopyranosyl-9,10-dihydro- 3,5,6,8-tetrahydroxy-1-methyl-9,10- dioxoanthracenecarboxylic acid - |IUPACnév = 2-[(4''S'')-4-<nowiki>[[</nowiki>(1''S'')-1-ethoxycarbonyl-3-phenyl-propyl]amino]- 3-oxo-2-azabicyclo[5.4.0]undeca-7,9,11-trien-2-y l]acetic acid - |IUPACName= (2''R'',6''S'',7a''R'')-2- [(1''E'',3''E'',5''E'',7''E'',9''E'',11''E'',13''E'',15''E'')- 16-[(1''R'',4''R'')-4-Hidroxi- 2,6,6-trimetil-1-ciklohex- 2-enil]-1,5,10,14- tetrametilhexadeka- 1,3,5,7,9,11,13,15- oktaenil]-4,4,7a-trimetil-2,5,6,7- tet rahidrobenzofurán-6-ol - | 4-[18-(4-hidroxy-2,6,6-trimetil-1-ciklohexenil) -3,7,12,16-tetrametil-oktadeca -1,3,5,7,9,11,13,15,17-nonaenil] -3,5,5-trimetil-ciklohex-2-en-1-o l - | IUPACName = ''(R)''-3,5,5-Trimetil-4-[3,7,12,16- tetrametil-18-(2,6,6-trimetilciklohex- 1-enyl)-octadeca-1,3,5,7,9,11,13,15,17 - nonaenil]-ciklohex-3-enol - |IUPACName=(1S,4S,6R)-1-[(1E,3E,5E,7E,9E,11E,13E,15E,17E)-18-[(1S,4S,6R)-4-Hydroxy-2,2,6-trimethyl-7-oxabicyclo[4.1.0]heptan-1-yl]-3,7,12,16-tetram ethyloctadeca-1,3,5,7,9,11,13,15,17-nonaenyl]-2,2,6-trimethyl-7-oxabicyclo[4.1.0]heptan-4-ol - | IUPACName = 6,6,9-trimetil-3-pentil-6''H''-benzo[c]kromén-1-ol - | IUPACName = 6,6,9-trimetil-3-propil-6''H''-benzo[''c'']kromén-1-ol - |IUPACnév = 6a,7,8,10a-tetrahydro-1-hydroxy-6,6-dimethyl-3-pentyl- 6H-Dibenzo[b,d]pyran-9-methanol - | [[IUPAC]] név || (6a''S'',10a''S'')-6,6,9-trimethyl-3-propyl-6a,7,8,10a- tetrahydro-6''H''-benzo[''c'']chromen-1-ol - 3,4,5-tris(2-methylpropanoyloxy)oxan-2-yl]oxy -4-(2-methylpropanoyloxy)-5-(2 - |IUPACName={[3-phenyl-1-{[(2''S'',3''R'',4''S'',5''S'',6''R'') -3,4,5-trihydroxy-6-(hydroxymethyl)-

3 7

W.: Aw: Re: Vital sign
by info＠gno.de 09 Aug '16

09 Aug '16

----- Original Nachricht ---- Von: Jan Dudík <jan.dudik(a)gmail.com> An: Pywikibot discussion list <pywikibot(a)lists.wikimedia.org> Datum: 08.08.2016 23:09 Betreff: Re: [pywikibot] Vital sign > I am only user, not developer. And it seems to me there is many changes > around some pyflakes, travis, test and some other weird stuff, but there Is that really true? 50% of all committed patches of the last 3 months depends on the framework and it's scripts, 10% where for scripts only, 30% where for tests which are important for the validity of methods and the rest where documentation and cosmetic changes. A lot of them where bugfixes. Anyway I agree the delay to solve bugs is increasing in the last months and the merged commits are decreasing a lot in the past. There where the lowest amount of commits since start of the project which was nearby 50 commit per month this year whereas we had 100-150 each month in the last ten years (in summary for the master branches of compat and core). 6 Developers make 75% of the commits but the main authors changes after 2 or 3 years. Peer group review is good for good quality code and to prevent malfunctions but it leads to a delayed commit if any. We have 21 developers with CR+2 right but only few use it. I propose to give CR+2 access to some new coders like - Lokal Profil - Dalba - Whym if they and the community agree. Anyway that doesn't really help you with your scripts but it could help for the current review process. Best xqt

1 0

Re: [pywikibot] pywikibot Digest, Vol 109, Issue 3
by Dr. Trigon 09 Aug '16

09 Aug '16

It was around 2014 when I dropped out of pywikibot (last time) partly due to a missing management. Some people where working on compat some on core - depending on who you asked the focus was either compat or core (or git migration). IMHO at that time a lot of unecessary additional load was created by decicions that never have been discussed truly. There was never a plan or schedule on how to proceed or what to work on. It was like "Oh, did you see that API change? We have to catch up and fix wikipedia.py." An thus some people kind of counteracted ("commit" war) each other. Essentially the one having most free time to invest boarded the ship. As long as you work on your small piece of code and do not interfere with others it's fine but if you do - good luck... ;) Everybody just works on and cares for its "own few pieces of code" in there and thus prefer to judge the style most. I would vote for some minimal leadership/management and that people working on basic or fundamental code (affecting everybody else) have to come together and reach an agreement first (before starting to code) and make it public. A long time ago I proposed a draft of a code of conduct I wanted the community to write and then to (optionally) agree on. A style guide should be part of that. We are to many developpers, having fluctuations etc. we need to give us a constitution. Dr. Trigon >Message: 5 >Date: Sun, 07 Aug 2016 15:01:50 +0000 >From: Amir Ladsgroup <ladsgroup(a)gmail.com> >To: Pywikibot discussion list <pywikibot(a)lists.wikimedia.org> >Subject: Re: [pywikibot] Vital sign >Message-ID: > <CA+ttme1m6-N57L14hHKyn088i38kUj4XNhqoHAdfu42Nvqf_xw(a)mail.gmail.com> >Content-Type: text/plain; charset="utf-8" > >I've been worried about this project for a very long time. I checked >out >slowly from pywikibot and I expressed my concerns to the developer >relations team privately but after this bug [1], I think it's time to >speak >out. >Disclaimer: I'm not saying pywikibot is dying or will die soon. I'm >saying >this project is going in unhealthy direction. I'm not de-valuing other >people's work and I think they are great but they are missing a few >steps >that other projects don't. > >1- Pywikibot has the biggest number of open patchsets after >mediawiki/core. >You might say, it's okay. Pywikibot is completely volunteer-based but >ratio >of distinct users / open patchsets is horrifyingly high. Meaning we >have >some developers that make a patch and they don't engage in reviewing >them >even if the patch got -1 or -2 (and funnier sometime they -1 or -2 >their >own patches) and move on to making other patches. Most of them end up >in a >obsolete situation needing a rebase or not needed anymore. >2- Developers don't engage in dialogue in proper places so others don't >know about issues. No one can subscribe to the phabricator board, it's >too >big but it would be nice to bring some discussions here. >3- No active developer is connected to other part of wikimedia projects >like listening to api announcements. >4- (Sometimes) It's a hostile environment. Behavior of other developers >sometimes is demotivating. >5- There's no ArchCom here. I have an approach which might be wrong but >another developer comes and disagrees and suggests another approach. I >don't like it but there is no place to give the last call so it'll stay >at >-1 or -2 mode forever. TLDR: Sometimes I feel someone just owns the >project >and makes patches stuck just by disagreeing on the approach. >6- There is no, absolutely not, a single guide on how to code review. I >know code review sucks in Wikimedia technical projects but this one is >another level. People send out -2 because "the syntax is ugly" (and the >patch is not a fifty nested loops, it's a['foo'] = 1 instead of >a['foo'] = >True). Mostly they just care about style rather than bugs. > >[1]: https://phabricator.wikimedia.org/T142155 > >I might be wrong and/or out-dated. Correct me please. > >Best > >On Sun, Aug 7, 2016 at 6:59 PM Bináris <wikiposta(a)gmail.com> wrote: > >> How is it possible that I haven't got any mail from this list since >> January? Is it dead or have I dropped out? >> >> -- >> Bináris >> _______________________________________________ >> pywikibot mailing list >> pywikibot(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/pywikibot >> >

1 0

[Pywikipedia-announce] Login broken for bots
by Maarten Dammers 07 Aug '16

07 Aug '16

Hi everyone, A change was deployed which changed the behavior of the login api. As a result Pywikibot bots can't login to any of the WMF wiki's. I asked Brad to undo his change so bots can login again. This problem is being tracked in https://phabricator.wikimedia.org/T142155 . Maarten _______________________________________________ pywikibot-announce mailing list pywikibot-announce(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/pywikibot-announce

5 7

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

pywikibot August 2016