Re: Compiling python on windows with vs

[Inada Naoki via Python-list]

> Since Git enables Windows NTFS case sensitivity while checking out sources

I didn't know that. Would you give us a link to this feature?
As far as I know, `git config core.ignorecase` doesn't mean NTFS case
sensitive.

On Wed, Jun 14, 2023 at 1:57 AM Thomas Schweikle via Python-list <
python-list@python.org> wrote:

> Hi!
>
> Trying to compile python on windows leads to following error:
>
>_testimportmultiple.vcxproj ->
>
> C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\amd64\_testimportmultiple.pyd
>_testmultiphase.c
>   Bibliothek
> "C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\amd64\_testmultiphase.lib"
>
> und Objekt "C:\Users\sct-muc\Docume
>nts\Projekte\cpython\PCbuild\amd64\_testmultiphase.exp" werden erstellt.
>Code wird generiert.
>Codegenerierung ist abgeschlossen.
>_testmultiphase.vcxproj ->
>
> C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\amd64\_testmultiphase.pyd
>_testconsole.c
> C:\Users\sct-muc\Documents\Projekte\cpython\PC\_testconsole.c(13,10):
> fatal  error C1083: Datei (Include) kann nicht geöffnet werde
> n: "..\modules\_io\_iomodule.h": No such file or directory
> [C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\_testconsole.vcxpro
> j]
>
> Fehler beim Buildvorgang.
>
> if I rename "Modules" to "modules" it will find
> "..\modules\_io\_iomodule.h" but wont find "..\Modules\..."
>
> Since Git enables Windows NTFS case sensitivity while checking out
> sources ... is it a bug or a "feature"? And: is there a simple
> workaround available besides disabling case sensitivity (which will
> break others)?
> --
> Thomas
>
> --
> https://mail.python.org/mailman/listinfo/python-list
>


-- 
Inada Naoki  
-- 
https://mail.python.org/mailman/listinfo/python-list

RE: Fwd: AUTO EDITOR DIDN'T WORK

[AVI GROSS via Python-list]

I think it is time to ask this topic to go find some other place to talk to 
itself.

I have seen NO reason to think any question about problems with Python has been 
asked. Not properly.

It sounds like someone messed up an installation, perhaps of other programs 
like an editor and some unspecified thing does not work. I suggest they start 
over and be careful so that if some specific version of Python is needed, it 
gets installed in the right place and so on. We here cannot be expected to have 
much idea about programs that perhaps we do not use.

Python can be used to build an editor, or parts it runs when needed, and it can 
be used to create or consume XML, or do things with audio formats. So can many 
other languages. If it was needed here and the setup was wrong or sabotaged, 
that is not something easily handled here.

Or did I miss something? If so, I know others here also missed it too.

If there is a more specific problem like some lines of actual python code not 
doing what was expected, please share that specifically with enough detail.


-Original Message-
From: Python-list  On 
Behalf Of Thomas Passin via Python-list
Sent: Tuesday, June 13, 2023 10:18 PM
To: python-list@python.org
Subject: Re: Fwd: AUTO EDITOR DIDN'T WORK

On 6/13/2023 9:43 PM, gene heskett via Python-list wrote:
> On 6/13/23 19:10, Thomas Passin via Python-list wrote:
>> On 6/13/2023 5:32 PM, Alan Gauld via Python-list wrote:
>>> Okay thanks. Meanwhile, I am not tech savvy so I may not say much here.
>>> I followed all the commands as given on the website to install auto
>>> editor standing it on python but after rendering the XML file, I
>>> couldn't open it with my Davinci Resolve 18. I uninstalled and
>>> reinstalled about twice and still no success hence I uninstalled it.
>>
>> I don't understand when you talk about an "XML file". Auto-editor 
>> works on video files, or at least .mp4 files, which are not XML files. 
>> Davinci Resolve does have some ability to interoperate with other 
>> editors using XML in some way (according to Wikipedia, 
>> https://en.wikipedia.org/wiki/DaVinci_Resolve) but that's a different 
>> thing completely.
>>
>> I also don't know what you mean by "after rendering the XML file" 
>> since from what I can see auto-edit doesn't render anything.
>>
>> The simplest thing that auto-editor can do is to cut out long periods 
>> of dead space, e.g., from an mp4 file.  Their documentation shows how 
>> to do it.  If it were me, I would run the example command line on a 
>> sample mp4 file, then see what it looked like in Davinci.  Is that 
>> what you did? It should be the same video but with some dead space 
>> removed.
>>
>> (Note that I'm speaking from a place of no experience with either of 
>> these software packages; just looking at what auto-edit claims to do).
>>
>>
>>
> auto-edit? Never heard of it. xml? I've written hundred of kilobytes of 
> it in plain old geany. I didn't know there was a special editor for xml.

Oh, there are, there are - mostly intended for document authoring, I think.

-- 
https://mail.python.org/mailman/listinfo/python-list

-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Fwd: AUTO EDITOR DIDN'T WORK

[Thomas Passin via Python-list]

On 6/13/2023 9:43 PM, gene heskett via Python-list wrote:

On 6/13/23 19:10, Thomas Passin via Python-list wrote:

On 6/13/2023 5:32 PM, Alan Gauld via Python-list wrote:

Okay thanks. Meanwhile, I am not tech savvy so I may not say much here.
I followed all the commands as given on the website to install auto
editor standing it on python but after rendering the XML file, I
couldn't open it with my Davinci Resolve 18. I uninstalled and
reinstalled about twice and still no success hence I uninstalled it.


I don't understand when you talk about an "XML file". Auto-editor 
works on video files, or at least .mp4 files, which are not XML files. 
Davinci Resolve does have some ability to interoperate with other 
editors using XML in some way (according to Wikipedia, 
https://en.wikipedia.org/wiki/DaVinci_Resolve) but that's a different 
thing completely.


I also don't know what you mean by "after rendering the XML file" 
since from what I can see auto-edit doesn't render anything.


The simplest thing that auto-editor can do is to cut out long periods 
of dead space, e.g., from an mp4 file.  Their documentation shows how 
to do it.  If it were me, I would run the example command line on a 
sample mp4 file, then see what it looked like in Davinci.  Is that 
what you did? It should be the same video but with some dead space 
removed.


(Note that I'm speaking from a place of no experience with either of 
these software packages; just looking at what auto-edit claims to do).




auto-edit? Never heard of it. xml? I've written hundred of kilobytes of 
it in plain old geany. I didn't know there was a special editor for xml.


Oh, there are, there are - mostly intended for document authoring, I think.

--
https://mail.python.org/mailman/listinfo/python-list

Re: Fwd: AUTO EDITOR DIDN'T WORK

[gene heskett via Python-list]

On 6/13/23 19:10, Thomas Passin via Python-list wrote:

On 6/13/2023 5:32 PM, Alan Gauld via Python-list wrote:

Okay thanks. Meanwhile, I am not tech savvy so I may not say much here.
I followed all the commands as given on the website to install auto
editor standing it on python but after rendering the XML file, I
couldn't open it with my Davinci Resolve 18. I uninstalled and
reinstalled about twice and still no success hence I uninstalled it.


I don't understand when you talk about an "XML file". Auto-editor works 
on video files, or at least .mp4 files, which are not XML files. Davinci 
Resolve does have some ability to interoperate with other editors using 
XML in some way (according to Wikipedia, 
https://en.wikipedia.org/wiki/DaVinci_Resolve) but that's a different 
thing completely.


I also don't know what you mean by "after rendering the XML file" since 
from what I can see auto-edit doesn't render anything.


The simplest thing that auto-editor can do is to cut out long periods of 
dead space, e.g., from an mp4 file.  Their documentation shows how to do 
it.  If it were me, I would run the example command line on a sample mp4 
file, then see what it looked like in Davinci.  Is that what you did? It 
should be the same video but with some dead space removed.


(Note that I'm speaking from a place of no experience with either of 
these software packages; just looking at what auto-edit claims to do).




auto-edit? Never heard of it. xml? I've written hundred of kilobytes of 
it in plain old geany. I didn't know there was a special editor for xml.


Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page 

--
https://mail.python.org/mailman/listinfo/python-list

Re: Fwd: AUTO EDITOR DIDN'T WORK

[Thomas Passin via Python-list]

On 6/13/2023 5:32 PM, Alan Gauld via Python-list wrote:

Okay thanks. Meanwhile, I am not tech savvy so I may not say much here.
I followed all the commands as given on the website to install auto
editor standing it on python but after rendering the XML file, I
couldn't open it with my Davinci Resolve 18. I uninstalled and
reinstalled about twice and still no success hence I uninstalled it.


I don't understand when you talk about an "XML file". Auto-editor works 
on video files, or at least .mp4 files, which are not XML files. 
Davinci Resolve does have some ability to interoperate with other 
editors using XML in some way (according to Wikipedia, 
https://en.wikipedia.org/wiki/DaVinci_Resolve) but that's a different 
thing completely.


I also don't know what you mean by "after rendering the XML file" since 
from what I can see auto-edit doesn't render anything.


The simplest thing that auto-editor can do is to cut out long periods of 
dead space, e.g., from an mp4 file.  Their documentation shows how to do 
it.  If it were me, I would run the example command line on a sample mp4 
file, then see what it looked like in Davinci.  Is that what you did? 
It should be the same video but with some dead space removed.


(Note that I'm speaking from a place of no experience with either of 
these software packages; just looking at what auto-edit claims to do).




--
https://mail.python.org/mailman/listinfo/python-list

Fwd: AUTO EDITOR DIDN'T WORK

[Alan Gauld via Python-list]

Forwarding to list

Okay thanks. Meanwhile, I am not tech savvy so I may not say much here.
I followed all the commands as given on the website to install auto
editor standing it on python but after rendering the XML file, I
couldn't open it with my Davinci Resolve 18. I uninstalled and
reinstalled about twice and still no success hence I uninstalled it.

On Mon, 12 Jun 2023, 23:33 Alan Gauld via Python-list,
mailto:python-list@python.org>> wrote:


On 12/06/2023 10:26, Real Live FootBall Tv via Python-list wrote:

> I did it because I was going to use it with another application, A
VIDEO
> EDITING APP, Auto EDITOR but it didn't work for some reasons
unknown to me.

You need to define "didn't work"
Did it work as a python interpreter?
ie. Did you get a >>> prompt in a terminal?
and without involvement from your video editor?
If so, what did you do to link it to the video editor?
And what was the result?

Or did Python not even start? How did you try to use it?
What OS are you on? Did the installer run OK?


-- Alan G
Author of the Learn to Program web site
http://www.alan-g.me.uk/ 
http://www.amazon.com/author/alan_gauld

Follow my photo-blog on Flickr at:
http://www.flickr.com/photos/alangauldphotos




-- https://mail.python.org/mailman/listinfo/python-list


-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Compiling python on windows with vs

[Thomas Schweikle via Python-list]

Am Di., 13.Juni.2023 um 20:36:17 schrieb Mats Wichmann via Python-list:

On 6/13/23 12:12, Thomas Schweikle via Python-list wrote:



Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz:

What version of visual studio are you using?


Visual Studio 2022, aka 17.6.2.


What version of python?


python 3.10.11 or 3.11.4

I’ve had success with using the cython package in python and cl from 
visual studio, but I haven’t tried visual studio alone.


Same problem at the same place: directory "../modules/..." not found, 
Renaming it from "Modules" to "modules" it is found, but then fails to 
find "Modules".


Looks like it awaits, compiling in Windows an filesystem only case 
aware, not case sensitive -- I'm assuming this a bug now. Building 
within cygwin (or MSYS, Ubuntu) this works as expected. But there it 
does not search for "modules" once and "Modules" at an other place.


I just did this build the other day for the first time even from a git 
checkout (so VS22, and not a versioned release but top of main branch), 
and there was no such problem - did you follow the instructions at 
https://devguide.python.org/getting-started/setup-building/index.html?


Yes.
Had git installed (2.41.0.windows.1), did "git clone 
https://github.com/python/cpython.git;, then checked out the branch I 
wanted: "git checkout 3.10.12" (or 3.11.4, 3.12.0b2).


Python was already installed and in path:
"python --version" gives back: "Python 3.11.4"

Changed into cpython directory, then called: ".\PCbuild\build.bat" 
(".\pcbuild\build.bat" will, within cmd.exe, throw an error: File not 
found -- remember directory cpython and all beyond are case sensitive, 
not only case aware -- git sets case sensitiveness for checked out 
directories).


It compiles until it does not find "modules", because the directory is 
named "Modules" (all posix file systems behave this way and NTFS can be 
forced to behave this way too. It is easy and any user can do it:


"fsutil.exe file SetCaseSensitiveInfo  enable"

You may query this with:

"fsutil.exe file queryCaseSensitiveInfo "

In my case:
~/Documents/Projekte/cpython> fsutil.exe file queryCaseSensitiveInfo .
Das Attribut für Groß-/Kleinschreibung für das Verzeichnis ^
"C:\Users\user\Documents\Projekte\cpython" ist aktiviert.

Or: the directory we're in is case sensitive and distinguishes between 
"Modules", "modules" and "MODULES" and you can have them all:


C:\Users\user\Documents\Projekte\cpython>dir
 Datenträger in Laufwerk C: ist Windows
 Volumeseriennummer: BC5E-F466

 Verzeichnis von C:\Users\user\Documents\Projekte\cpython

Di, 13.Jun.2023  21:23  .
Di, 13.Jun.2023  21:23  ..
[...]
Di, 13.Jun.2023  21:23  MODULES
Mo, 12.Jun.2023  22:13  Modules
Di, 13.Jun.2023  21:23  modules
[...]
  16 Datei(en),  1.320.340 Bytes
  21 Verzeichnis(se), 134.699.622.400 Bytes frei

Since case sensitivity is necessary for a variety of projects normally 
only used with *nix-OS I've configured git to create directories with 
case sensitivity set enabled (its default meanwhile if git is installed 
on windows).

--
Thomas



OpenPGP_signature
Description: OpenPGP digital signature
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Compiling python on windows with vs

[Eryk Sun via Python-list]

On 6/13/23, Thomas Schweikle via Python-list  wrote:
>
> Since Git enables Windows NTFS case sensitivity while checking out
> sources ... is it a bug or a "feature"? And: is there a simple

AFAIK the Windows version of Git (you're not using the Linux version
of Git via WSL, right?) does not automatically enable NTFS case
sensitivity. But a newly created directory does inherit the case
sensitivity of its parent directory. Make sure to clone the CPython
repo in a directory that has case sensitivity disabled.

>_testconsole.c
> C:\Users\sct-muc\Documents\Projekte\cpython\PC\_testconsole.c(13,10):
> fatal  error C1083: Datei (Include) kann nicht geöffnet werde
> n: "..\modules\_io\_iomodule.h": No such file or directory
> [C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\_testconsole.vcxpro
> j]

I just built the main branch in a case sensitive tree. I had no
problem building "_testconsole.c". However, building the _decimal
extension module raised a couple of serious warnings. In
"PCbuild/_decimal.vcxproj", there's an include for
"..\Modules\_decimal\libmpdec\vcdiv64.asm". However, MSBuild resolved
this relative path with all lower-case names, i.e. "modules" instead
of the correct name "Modules", and it incorrectly tried to output
"vcdiv64.obj" in a subdirectory of "pcbuild" instead of the correct
name "PCbuild". This appears to be a bug in MSBuild. A lot of Windows
programs don't handle case-sensitive directories well, including
Python's standard library. It's understandable when comparing paths,
but the behavior in this case is inexcusably bad.
-- 
https://mail.python.org/mailman/listinfo/python-list

RE: Compiling python on windows with vs

[Jim Schwartz via Python-list]

One expert told me to do the following when compiling via cython and cl:

cython -3 --embed -o c_file_namepython_file_name

Then, assuming python is installed in your apps directory and not your program 
files directory:

set "PYTHON_DIR=%LocalAppData%\Programs\Python\Python311" 

or whatever directory you put python in.

cl /O2 /I"%PYTHON_DIR%\Include" c_file_name  /link /libpath:"%PYTHON_DIR%\libs"

If that doesn't work, that's all I have.  Sorry.

-Original Message-
From: Python-list  On 
Behalf Of Thomas Schweikle via Python-list
Sent: Tuesday, June 13, 2023 1:12 PM
To: Python 
Cc: Thomas Schweikle 
Subject: Re: Compiling python on windows with vs



Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz:
> What version of visual studio are you using?

Visual Studio 2022, aka 17.6.2.

> What version of python?

python 3.10.11 or 3.11.4

> I’ve had success with using the cython package in python and cl from visual 
> studio, but I haven’t tried visual studio alone.

Same problem at the same place: directory "../modules/..." not found, Renaming 
it from "Modules" to "modules" it is found, but then fails to find "Modules".

Looks like it awaits, compiling in Windows an filesystem only case aware, not 
case sensitive -- I'm assuming this a bug now. Building within cygwin (or MSYS, 
Ubuntu) this works as expected. But there it does not search for "modules" once 
and "Modules" at an other place.

>> On Jun 13, 2023, at 11:59 AM, Thomas Schweikle via Python-list 
>>  wrote:
>>
>> Fehler beim Buildvorgang
--
Thomas


-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Compiling python on windows with vs

[Mats Wichmann via Python-list]

On 6/13/23 12:12, Thomas Schweikle via Python-list wrote:



Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz:

What version of visual studio are you using?


Visual Studio 2022, aka 17.6.2.


What version of python?


python 3.10.11 or 3.11.4

I’ve had success with using the cython package in python and cl from 
visual studio, but I haven’t tried visual studio alone.


Same problem at the same place: directory "../modules/..." not found, 
Renaming it from "Modules" to "modules" it is found, but then fails to 
find "Modules".


Looks like it awaits, compiling in Windows an filesystem only case 
aware, not case sensitive -- I'm assuming this a bug now. Building 
within cygwin (or MSYS, Ubuntu) this works as expected. But there it 
does not search for "modules" once and "Modules" at an other place.


I just did this build the other day for the first time even from a git 
checkout (so VS22, and not a versioned release but top of main branch), 
and there was no such problem - did you follow the instructions at 
https://devguide.python.org/getting-started/setup-building/index.html?



--
https://mail.python.org/mailman/listinfo/python-list

Re: Compiling python on windows with vs

[Thomas Schweikle via Python-list]

Am Di., 13.Juni.2023 um 19:20:38 schrieb Jim Schwartz:

What version of visual studio are you using?


Visual Studio 2022, aka 17.6.2.


What version of python?


python 3.10.11 or 3.11.4


I’ve had success with using the cython package in python and cl from visual 
studio, but I haven’t tried visual studio alone.


Same problem at the same place: directory "../modules/..." not found, 
Renaming it from "Modules" to "modules" it is found, but then fails to 
find "Modules".


Looks like it awaits, compiling in Windows an filesystem only case 
aware, not case sensitive -- I'm assuming this a bug now. Building 
within cygwin (or MSYS, Ubuntu) this works as expected. But there it 
does not search for "modules" once and "Modules" at an other place.



On Jun 13, 2023, at 11:59 AM, Thomas Schweikle via Python-list 
 wrote:

Fehler beim Buildvorgang

--
Thomas



OpenPGP_signature
Description: OpenPGP digital signature
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Compiling python on windows with vs

[Jim Schwartz via Python-list]

What version of visual studio are you using?  What version of python?  I’ve had 
success with using the cython package in python and cl from visual studio, but 
I haven’t tried visual studio alone. 

Sent from my iPhone

> On Jun 13, 2023, at 11:59 AM, Thomas Schweikle via Python-list 
>  wrote:
> 
> Fehler beim Buildvorgang

-- 
https://mail.python.org/mailman/listinfo/python-list

Compiling python on windows with vs

[Thomas Schweikle via Python-list]

Hi!

Trying to compile python on windows leads to following error:

  _testimportmultiple.vcxproj -> 
C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\amd64\_testimportmultiple.pyd

  _testmultiphase.c
 Bibliothek 
"C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\amd64\_testmultiphase.lib" 
und Objekt "C:\Users\sct-muc\Docume

  nts\Projekte\cpython\PCbuild\amd64\_testmultiphase.exp" werden erstellt.
  Code wird generiert.
  Codegenerierung ist abgeschlossen.
  _testmultiphase.vcxproj -> 
C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\amd64\_testmultiphase.pyd

  _testconsole.c
C:\Users\sct-muc\Documents\Projekte\cpython\PC\_testconsole.c(13,10): 
fatal  error C1083: Datei (Include) kann nicht geöffnet werde
n: "..\modules\_io\_iomodule.h": No such file or directory 
[C:\Users\sct-muc\Documents\Projekte\cpython\PCbuild\_testconsole.vcxpro

j]

Fehler beim Buildvorgang.

if I rename "Modules" to "modules" it will find 
"..\modules\_io\_iomodule.h" but wont find "..\Modules\..."


Since Git enables Windows NTFS case sensitivity while checking out 
sources ... is it a bug or a "feature"? And: is there a simple 
workaround available besides disabling case sensitivity (which will 
break others)?

--
Thomas



OpenPGP_signature
Description: OpenPGP digital signature
-- 
https://mail.python.org/mailman/listinfo/python-list