On 10/9/19, Malcolm Greene wrote:
>
> @Dan: Yes, symlinks would be a good work around.
Assuming the file system supports symlinks (e.g. NTFS, but not FAT32),
a relative symlink in the directory beside python.exe works fine, e.g.
"python3.exe" -> "python.exe". Putting the symlink in another
direct
Thanks Paul and Dan.
@Paul: Yes, it *IS* a bit confusing . Your pip explanation hit the spot.
@Dan: Yes, symlinks would be a good work around.
Malcolm
--
https://mail.python.org/mailman/listinfo/python-list
No, the Windows builds do not provide versioned executables
(python3.exe or python3.7.exe). Generally, the recommended way to
launch Python on Windows is via the py.exe launcher (py -3.7, or just
py for the default), but if you have Python on your PATH then python
works.
The reason pip has version
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Malcolm Greene wrote:
> I'm jumping between Linux, Mac and Windows environments. On Linux and
> Mac we can invoke Python via python3 but on Windows it appears that
> only python works. Interestingly, Windows supports both pip and pip3
> flavors. Am I
I'm jumping between Linux, Mac and Windows environments. On Linux and Mac we
can invoke Python via python3 but on Windows it appears that only python works.
Interestingly, Windows supports both pip and pip3 flavors. Am I missing
something? And yes, I know I can manually create a python3 alias by
Hello all,
We are rebooting the original Python user group, Python West Midlands,
yay! Our first event is on Saturday 9th November 2019 in Birmingham
city centre.
The event is open to all levels, from never programmed before through
to professional developers and Python core developers. Bring you
Wing Python IDE version 7.1.2 has been released. It adds a How-To for
using Wing with Docker, allows disabling code warnings from the tooltip
displayed over the editor, adds support for macOS 10.15 (Catalina),
supports code folding in JSON files, adds optional word wrapping for
output in the T
On 08/10/2019 15:05, Bill Deegan wrote:
You might just consider working with the BuildBot project to add support
for lighter weight build workers.
Re-Re-Re-inventing the wheel is almost always wasted effort.
Buildbot looks good. I'll check to make sure its open source license is
compatible w
On 08/10/2019 13:17, Rhodri James wrote:
On 08/10/2019 11:22, Simon Connah wrote:
I'm posting this message as a way to gauge interest in the project
and to see if it is worth moving forward with. There are probably
hundreds of CI/CD tools out there and many more general devops tools
but what
Antoon Pardon wrote:
> I have some logging utilities so that when I write library code, I just
> use the following.
>
> from logutil import Logger
>
> log = Logger(__name__)
If logutil is under your control you can make log a callable object with a
tracing method:
[logutil.py]
class Logger:
On Wed, Oct 9, 2019 at 9:53 PM Antoon Pardon wrote:
>
> I have some logging utilities so that when I write library code, I just use
> the following.
>
> from logutil import Logger
>
> log = Logger(__name__)
Are you always absolutely consistent with this? Do you always have it
as a module-level v
I have some logging utilities so that when I write library code, I just use the
following.
from logutil import Logger
log = Logger(__name__)
And from then on I just use log, to do the logging of that module.
But now I would like to write a decorator trace, so that a decorated
function would lo
12 matches
Mail list logo
