[issue21613] Installer for mac doesn't store the installation location

[Artem Ustinov]

New submission from Artem Ustinov:

I'm trying to automate the Python uninstallation on mac but I've found that the 
actual installation location is not stored for Python packages.
That location is required since the pkgutil keeps track of installed files (if 
you run $ pkgutil --files org.python.Python.PythonFramework-3.4) but doesn't 
store the absolute paths for that files.


1. Run $ pkgutil --pkgs=.*Python.*3\.4
Here's the expected output
org.python.Python.PythonApplications-3.4
org.python.Python.PythonDocumentation-3.4
org.python.Python.PythonFramework-3.4
org.python.Python.PythonInstallPip-3.4
org.python.Python.PythonProfileChanges-3.4
org.python.Python.PythonUnixTools-3.4

2. Run $ pkgutil --pkg-info org.python.Python.PythonFramework-3.4
Here's the output
package-id: org.python.Python.PythonFramework-3.4
version: 3.4.1
volume: /
location: (null)
install-time: 1401373546

Actual Result: The location property is (null)
Expected Result: The location property should be 
'/Library/Frameworks/Python.framework'

--
assignee: ronaldoussoren
components: Installation, Macintosh
messages: 219393
nosy: ronaldoussoren, ustinov
priority: normal
severity: normal
status: open
title: Installer for mac doesn't store the installation location
type: behavior
versions: Python 3.2, Python 3.3, Python 3.4

___
Python tracker 
<http://bugs.python.org/issue21613>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19462] Add remove_argument() method to argparse.ArgumentParser

[Artem Ustinov]

Artem Ustinov added the comment:

It does the trick with optionals but not the positionals.
How the positional arguments can be removed/hidden?

--

___
Python tracker 
<http://bugs.python.org/issue19462>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19462] Add remove_argument() method to argparse.ArgumentParser

[Artem Ustinov]

Artem Ustinov added the comment:

What is the way to 'hide' the argument from being parsed?

E.g. we have self.parser.add_argument('foo') in parent class,
how can we modify it in child class so that it would not to
appear in --help strings and not populated to child's Namespace?

--

___
Python tracker 
<http://bugs.python.org/issue19462>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19462] Add remove_argument() method to argparse.ArgumentParser

[Artem Ustinov]

Artem Ustinov added the comment:

Paul,
essentialy, what i looking for is to replace the 'help' string of the
inherited argument with the new one. If you say it could be changed without
any effect so what would be the proper way to do it using argparse?
Artem

--

___
Python tracker 
<http://bugs.python.org/issue19462>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19462] Add remove_argument() method to argparse.ArgumentParser

[Artem Ustinov]

Artem Ustinov added the comment:

Explicitly substitute, excuse me
On 31 Oct 2013 20:11, "Artem Ustinov"  wrote:

>
> Artem Ustinov added the comment:
>
> We need argparse to raise an error for conflicting options and that's why
> we need to implicitly substitute an option when we need it
> On 31 Oct 2013 19:54, "R. David Murray"  wrote:
>
> >
> > R. David Murray added the comment:
> >
> > Does conflict_handler='resolve' address your use case?  It sounds like it
> > should.
> >
> > --
> > nosy: +r.david.murray
> >
> > ___
> > Python tracker 
> > <http://bugs.python.org/issue19462>
> > ___
> >
>
> --
>
> ___
> Python tracker 
> <http://bugs.python.org/issue19462>
> ___
>

--

___
Python tracker 
<http://bugs.python.org/issue19462>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19462] Add remove_argument() method to argparse.ArgumentParser

[Artem Ustinov]

Artem Ustinov added the comment:

We need argparse to raise an error for conflicting options and that's why
we need to implicitly substitute an option when we need it
On 31 Oct 2013 19:54, "R. David Murray"  wrote:

>
> R. David Murray added the comment:
>
> Does conflict_handler='resolve' address your use case?  It sounds like it
> should.
>
> --
> nosy: +r.david.murray
>
> ___
> Python tracker 
> <http://bugs.python.org/issue19462>
> ___
>

--

___
Python tracker 
<http://bugs.python.org/issue19462>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue19462] Add remove_argument() method to argparse.ArgumentParser

[Artem Ustinov]

New submission from Artem Ustinov:

In order to migrate from optparse to argparse we need to have an ability to 
substitute anguments, e.g. remove and then create.

In our framework we use the command line utility base class and then inherit 
the particular tools from it. The parser in base class uses add_argument() to 
populate the general argument list but for some tools it is needed to modify 
the inherited arguments set and make some arguments to have the modified 
meaning.

With optparse we've just used remove_option() and then added the modified one 
with add_option() but argparse currently does not have this functionality.

For the purpose above we just need to have remove_argument() or 
modify_argument() methods in orgparse

--
components: Library (Lib)
messages: 201832
nosy: ustinov
priority: normal
severity: normal
status: open
title: Add remove_argument() method to argparse.ArgumentParser
type: enhancement
versions: Python 3.2

___
Python tracker 
<http://bugs.python.org/issue19462>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com