On 2017-03-23, Klaus Jantzen wrote:
>>> And you would need tables showing which libraires are required for
>>> which Python features: tkinter is optional, crypto is optional (or
>>> at least used to be), etc.
>>
>> That's a good idea - that would make the simple table
On 03/23/2017 03:45 AM, Klaus Jantzen wrote:
The information must be somewhere because Python must have been compiled
frequently and correctly for the various (important) OSs before making
it available to the public. And I do not think that it is left up to
"your luck" that the required packages
On 03/23/2017 01:45 AM, Klaus Jantzen wrote:
> The information must be somewhere because Python must have been compiled
> frequently and correctly for the various (important) OSs before making
> it available to the public. And I do not think that it is left up to
> "your luck" that the required
On 03/23/2017 12:23 AM, Jon Ribbens wrote:
On 2017-03-22, Grant Edwards wrote:
On 2017-03-22, Thomas Nyberg wrote:
On 03/22/2017 03:22 PM, Jon Ribbens wrote:
A simple table with a list of the library names, the debian package
names, and the rpm
On Thu, Mar 23, 2017 at 10:50 AM, Nathan Ernst wrote:
> I would also add a link to the dependency's project page, in case building
> from source is necessary.
>
> You don't always have root, and you're not always building with the system
> supplied compiler.
>
> There are
I would also add a link to the dependency's project page, in case building
from source is necessary.
You don't always have root, and you're not always building with the system
supplied compiler.
There are a lot of situations that may require building from source. Far
too many to even bother to
On 2017-03-22, Grant Edwards wrote:
> On 2017-03-22, Thomas Nyberg wrote:
>> On 03/22/2017 03:22 PM, Jon Ribbens wrote:
>>> A simple table with a list of the library names, the debian package
>>> names, and the rpm names would provide the information
On Thu, Mar 23, 2017 at 7:34 AM, Thomas Nyberg wrote:
> On 03/22/2017 03:22 PM, Jon Ribbens wrote:
>>
>> A simple table with a list of the library names, the debian package
>> names, and the rpm names would provide the information in a way that
>> would be useful to everyone.
On 2017-03-22, Thomas Nyberg wrote:
> On 03/22/2017 03:22 PM, Jon Ribbens wrote:
>> A simple table with a list of the library names, the debian package
>> names, and the rpm names would provide the information in a way that
>> would be useful to everyone.
A _simple_ table
On 03/22/2017 03:22 PM, Jon Ribbens wrote:
A simple table with a list of the library names, the debian package
names, and the rpm names would provide the information in a way that
would be useful to everyone.
I definitely agree, but it would be kind of difficult to maintain. I
mean if you
On 03/22/2017 06:34 PM, Thomas Nyberg wrote:
On 03/22/2017 12:42 PM, Klaus Jantzen wrote:
Hello,
in order to have the Python-SQLite support available one has to
recompile Python. For the recompiliation to succeed a number of
'modules/libs' have to be present.
On 2017-03-22, Thomas Nyberg wrote:
> I can't speak for the maintainers, but I don't think that providing such
> a list is super reasonable considering that there are many different OSs
> which have sometimes have slightly different library package names
> (though of course
On 03/22/2017 12:42 PM, Klaus Jantzen wrote:
Hello,
in order to have the Python-SQLite support available one has to
recompile Python. For the recompiliation to succeed a number of
'modules/libs' have to be present.
In the internet I found the following list
build-essential
libz-dev
Hello,
in order to have the Python-SQLite support available one has to
recompile Python. For the recompiliation to succeed a number of
'modules/libs' have to be present.
In the internet I found the following list
build-essential
libz-dev
libreadline-dev
libncursesw5-dev
libssl-dev
14 matches
Mail list logo