On 09/06/2020 23:49, Doug Henderson via Cygwin-apps wrote:
On Tue, 9 Jun 2020 at 09:56, marco atzeri via Cygwin-apps
wrote:
On Tue, Jun 9, 2020 at 3:23 PM Hamish McIntyre-Bhatty via Cygwin-apps wrote:
I suspect the user base is too small to justify the effort and I am afraid every
major
On Tue, 9 Jun 2020 at 09:56, marco atzeri via Cygwin-apps
wrote:
>
> On Tue, Jun 9, 2020 at 3:23 PM Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>>
>
> I suspect the user base is too small to justify the effort and I am afraid
> every
> major package needs a different approach.
I find that
On 09/06/2020 16:55, marco atzeri wrote:
> I suspect the user base is too small to justify the effort and I am afraid
> every
> major package needs a different approach.
> My octave and all other math programs know-how does not apply to the
> python effort I am working on ;-)
>
> From my side, I
On Tue, Jun 9, 2020 at 3:23 PM Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>
> In the process of making my cygport file for wxPython 4, I've quite
> quickly found that I don't understand how cygport works all that well.
>
> The reference guide is extremely useful, but it's a bit tricky finding
In the process of making my cygport file for wxPython 4, I've quite
quickly found that I don't understand how cygport works all that well.
The reference guide is extremely useful, but it's a bit tricky finding
which things are useful/relevant. Is there a user guide for
Cygport/could we make one
