[issue6860] Inconsistent naming of custom command in setup.py help output

2020-11-08 Thread Irit Katriel
Irit Katriel added the comment: As per Camilla's comment, this is no longer an issue. -- nosy: +iritkatriel resolution: accepted -> wont fix stage: needs patch -> resolved status: open -> closed ___ Python tracker

[issue6860] Inconsistent naming of custom command in setup.py help output

2015-10-27 Thread Camilla Montonen
Camilla Montonen added the comment: Apologies, I should have clarified: I can still replicate the bug in the original post, but I no longer believe this is an issue, because the wording in the documentation has been changed for Python 2.X https://docs.python.org/2/distutils/apiref.html#creatin

[issue6860] Inconsistent naming of custom command in setup.py help output

2015-10-27 Thread Camilla Montonen
Camilla Montonen added the comment: This is still an issue in Python 3.4.3, but I believe the relevant documentation has been changed already to alert users to the fact that the class name and the command name should be the same. Quoting from: https://docs.python.org/3/distutils/apiref.html#

[issue6860] Inconsistent naming of custom command in setup.py help output

2010-09-29 Thread Éric Araujo
Éric Araujo added the comment: This is a murky area, I’m not sure we have to refactor so much just to fix this bug. Maybe it’s a doc bug: People have to define command_name if their command has a name that is different from the class name. Maybe it’s a simple fix in the code for -h. I’d li

[issue6860] Inconsistent naming of custom command in setup.py help output

2010-09-29 Thread Éric Araujo
Changes by Éric Araujo : -- Removed message: http://bugs.python.org/msg102824 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue6860] Inconsistent naming of custom command in setup.py help output

2010-08-04 Thread Éric Araujo
Changes by Éric Araujo : -- stage: -> needs patch versions: +Python 2.5, Python 2.6, Python 3.1 ___ Python tracker ___ ___ Python-bugs

[issue6860] Inconsistent naming of custom command in setup.py help output

2010-04-11 Thread Éric Araujo
Éric Araujo added the comment: Hello Distutils being frozen, I’m reassigning to Distutils2. Not sure if I should make versions blank, 3.3 or third-party, so leaving it alone. Regards -- components: +Distutils2 -Distutils ___ Python tracker

[issue6860] Inconsistent naming of custom command in setup.py help output

2010-04-08 Thread Éric Araujo
Changes by Éric Araujo : -- nosy: +merwok ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue6860] Inconsistent naming of custom command in setup.py help output

2009-10-26 Thread Tarek Ziadé
Tarek Ziadé added the comment: It's a bit more complicated. the option you are desrcibing it just one way to register commands in fact. Distutils also has a discovery function that will load commands from packages, and that's where the biggest issue is. -- versions: -Python 3.1

[issue6860] Inconsistent naming of custom command in setup.py help output

2009-09-17 Thread Patrick Näf
Patrick Näf added the comment: >To be able to do this fix, I also need to change the way commands are >registered in Distutils. Hm, I thought commands were registered in the setup() function with the cmdclass dict. Like this: setup( # "test" is the name that should be used for display

[issue6860] Inconsistent naming of custom command in setup.py help output

2009-09-17 Thread Tarek Ziadé
Tarek Ziadé added the comment: To be able to do this fix, I also need to change the way commands are registered in Distutils. Right now, Distutils scans packages that were provided as "command packages" and just adds all commands from the namespace, using the class name. Which means there's no

[issue6860] Inconsistent naming of custom command in setup.py help output

2009-09-15 Thread Tarek Ziadé
Tarek Ziadé added the comment: Right, thanks for noticing this. Here's the change I am going to make: The code will use command.get_command_name() *everywhere* for the help display. This method implemented in Command does the following: - if the attribute "command_name" is present, it is re

[issue6860] Inconsistent naming of custom command in setup.py help output

2009-09-07 Thread Patrick Näf
New submission from Patrick Näf : The attached setup.py file defines a custom command named "test", which is implemented in a class named "TestClass". Try to run both of the following: 1) ./setup.py test -h 2) ./setup.py --help-commands In case 1, Distutils will use the class name to print the