Page MenuHomePhabricator

[BLOCKER] All scripts fails in compat with SVN
Closed, ResolvedPublic

Description

With removing .py files from i18n Directory all scripts fails in compat:

C:\pwb\SVN\compat>replace.py -regex "\((\d+?)\)" "[[\1]]"  -page:user:xqt/Test
Traceback (most recent call last):
  File "C:\pwb\SVN\compat\replace.py", line 969, in <module>
    main()
  File "C:\pwb\SVN\compat\replace.py", line 635, in main
    {'description': u''})
  File "C:\pwb\SVN\compat\pywikibot\i18n.py", line 338, in twtranslate
    transdict = getattr(__import__("i18n", {}, {}, [package]), package).msg
AttributeError: 'module' object has no attribute 'replace'

Event Timeline

Xqt raised the priority of this task from to High.
Xqt updated the task description. (Show Details)
Xqt added a project: Pywikibot-compat.
Xqt added subscribers: Xqt, valhallasw.
Restricted Application added subscribers: Aklapper, Unknown Object (MLST). · View Herald TranscriptMay 24 2015, 8:06 PM

In which branch is the i18n directory? Maybe it didn't switch to the 'compat' branch?

So the problem is that SVN external for i18n does not automatically change to use the git branch 'compat'. We can update the .svnprops file, but that may not automatically work for TortoiseSVN.

jayvdb renamed this task from [BLOCKER] All scripts Fails in compat to [BLOCKER] All scripts fails in compat with SVN.May 24 2015, 8:30 PM
jayvdb set Security to None.
jayvdb added a subscriber: Ladsgroup.

i18n is an external for both, compat an core. You cannot update the Settings and need a new directory for that stuff.
I guess it would be better to Keep the .py files until compat is finally closed.

Are there a lot of SVN users of compat?

I am one of them until all the scripts i use are ported to core.

I am user of compat (and SVN) for interwiki because of T99365#1293286

There are two different things: One is using compat and the other one is using SVN. Using compat for doing some tasks is reasonable while using SVN is not.

Using git was over my skills on windows (or over skills of my windows)

Ladsgroup, I disagree. Using svn is one of the proposed ways using the framework. And maybe for windows user it is the easiest way. And for my experiences it is the safest, clearest and best way if having local changes and running the not.

Anyway that patch was able to remove i18n files for git too which blocked all scripts except privat scripts who doesn't use translation.

And last, which is the disadvantage of keeping those files for core in that place?

Xqt claimed this task.

And btw I am running three or four private scripts 24/7 based on compat an few compat framework scripts when needed as long as they are brocken in core. The last I've found was checkinages.py, the next I am working on is fixes-redirect.py which uses imported compat methods. And there are some other features on other scripts which are not yet ported.
On the other hand I propose using core now and all of my newly written script uses the new framework with all of its advantages and disadvantages.