Is this still an issue?
I thought the latest version fixed it according to the github comments

why in API.py? Can't it be done in the login.py like how it was done in compact?

@Vyeshwant123 Sorry about that!
I'd recommend you go ahead and find another bug to solve :)

@Mpaa while I understand that you could solve this task in less than a minute, it would be useful to leave these good first task tasks for people who would like to begin contributing to pywikibot. Especially something like this low priority, easy task.

Can the critical bug fixes be mentioned by adding them as subtasks ? This would give more clarity to find things and also to see how close we are to the next release

Agree, that's a bit irritating, but as it's warnings it is not fatal.
I've created the task T146580 which will look into removing those warnings for image.py

Adding more context:

Marking as easy.
What essentially needs to be done is change the self.templatesWithParams() to self.templates() because we don't want the parameters which contain the target of the redirect.

By "document" what do you mean ? Where should this be documented ? What sort of information additionally should be added ?

I don't think this is a bug either. In fact, IMO this helps a lot in debugging when you want to understand the exact code paths

Seems like this can't really be solved easily as understanding "undesirable titles" is a difficult thing to be automated. Hence, human knowledge would be needed for this.
As @Ladsgroup mentioned, the script does as the user whether to create or not. So, I think this task should be closed ?

The codebase says that the function nicepath() is deprecated, and it is not being used by any of the scripts as of now in the scripts/. The only function using this in core is nice_get_address() ... which is also deprecated.

The only solution to this, as I see it would be to save all the items in a set() and check if the page has already been generated.

Works for me too, unable to reproduce this.
What version of pywikibot/python is this in ?

@MarcoAurelio can you check if you get this with the latest pywikibot code ? There is a commit on https://gerrit.wikimedia.org/r/#/c/282195/ which should have solved it.

This has been merged into the stable pytest 3.0
Closing the task

@Mpaa that did work for a resolution for 1 day.
For my purpose, 1Day is sufficient so I'm closing this task for the time being. If someone needs a smaller resolution it can be reopened.

@Umherirrender What exactly is Grade B ? I find that only Grade A, C, and X are mentioned at https://www.mediawiki.org/wiki/Compatibility

This issue was created in 2010, and I'm wondering whether it's still applicable.
At that time, IE8 or IE7 was the default in windows, and IE8 does not support CMYK, but later in 2011 IE9 was released with CMYK support. Do we have any data that anyone still uses IE8 and lower ? Do we still want to support it ?

@01tonythomas Thank you for the reminder. I thought I had updated it here, but I was mistaken. Updated the report for last week now.

@jayvdb From my understanding, OSX wheel are there. Here is a travis build with OSX, Py35: https://travis-ci.org/python-pillow/pillow-wheels/jobs/141359557

Currently ~/.local/share/file-metadata or something like that. It's the "default location" where the OS lets apps put user data into. (It's mentioned by the package called appdirs)

The simplest way to install openCV would be sudo apt-get install python-opencv. I'm still working on making dependency handling slightly better, along with https://github.com/AbdealiJK/file-metadata/issues/46

@DrTrigon Yes, matplotlib does not currently give suggestions. I've created https://github.com/matplotlib/matplotlib/pull/6575 for it

@DrTrigon you can find the code for that at https://github.com/AbdealiJK/file-metadata/blob/95cc2abb3506608266b1faf0da0722433ad6b03b/tests/bulk.py
Note that it has some extra args:

• -logname - The logname to write to. Used as -logname:Some_Name which tells it to write to User:<LoggedInUserInUserConfig>/logs/Some_Name.
• -dryrun - Print the log rather than writing to the userspace. needs to be used as -dryrun:1

Regarding Project Plan, second 50%, again: I think it would be worth it to spend some time revamping how the installation of dependencies happens (again).

To edit the code, you have 2 options:

Actually I haven't updated the requirements.txt on the pypi version or in master yet. Not sure what the issue was, but it seems like pip resolved it.

Ouch, sorry. just read the error message properly. It seems the Pillow version is really old ? (It doesn't seem to have a warning called DecompressionBombWarning). This was added in Pillow 2.5.0 according to release notes, I'll adding a minimum version in the requirements.txt.

Yeah, I think the pywikibot thing is a bit confusing too. I assumed pywikibot veterans would be trying that. I'd like @jayvdb 's opinion on how a script not inside /pywikibot/scripts is supposed to use pywikibot. Is there an example project I could look at ?

Ah.
I just realized that in your case, the reason the wheel is not being used is because you have a really old version of pip which does not support wheels.

@DrTrigon There is no special step involved for installing with wheels. pip install <pkg name> generally prefers using wheels if a wheel is found that is suitable for your system.
If a wheel suitable for your system is not found, it compiles it from source.

@DrTrigon wheels are like pre-compiled versions of a python package. As file-metadata does not need any compilation, it isnt very needed for our package. But our dependencies that have C code (skimage, numpy, scipy, dlib, matplotlib, wand) should normally have wheels to make it easy to install.

@DrTrigon The numpy issue, I think the error message is quite clear.

Issue 1:
Hm. So, the first issue is surprising. pypi normally does not guarantee the order of installation of packages.
So, if pkgA needs pkgB for compilation, this can be a problem.
Could you tell me which package gave an error about numpy not installed so I can investigate further ?

A few ideas that I've had for the next phase of the project which have been inspired by various things I've seen in the past few weeks:

I've made the modification in the "SSH" section of the Help page.

@zhuyifei1999 I did try dev.tools.wmflabs.org too. but that didn't seem to have much of an effect.

I do already have a ServerAliveInterval. And I tried values like 300, 200, 100. But I still get dropped frequently. Although I believe it has become better now compared to how it was before this.

This is an interesting question, and the major issue I see here is that the user's computer will hang if we do use it.

I have a few questions here, probably due to my lack of experience with externals: