EuroPython 2021: Launching the conference website
During the last few weeks the team has been hard at work making final changes to the website, and we are excited to announce the launch of the conference website for EuroPython 2021 today ! * EuroPython 2021 Conference Website * https://ep2021.europython.eu/ We have also migrated the accounts from last year's website to the new one, so you should be able to login right away. That said, we still recommend changing your password as best practice. If you don't have an account yet, you can easily create one to be ready for ticket sales. Quick Summary - EuroPython 2021 will be run online from July 26 - August 1: - Two workshop/training days (July 26 - 27) - Three conference days (July 28 - 30) - Two sprint days (July 31 - August 1) The sessions will be scheduled to ensure they are also accessible for those in the Asian and Americas time zones. More updates - Ticket sales will start on Monday, April 19. We have refined the ticket structure for EuroPython 2021 to make it easier to understand and added a table outlining the differences between the various ticket types. - Financial aid will once again be available, since we've grown our team. We'd like to enable more people from lower income countries to attend. Applications can be filed starting Wednesday, April 21. - The Call for Papers (CFP) will be opened on Monday, April 26. If you want to prepare, you can already have a look at the CFP page on the website. The CFP will stay open for two weeks. A mentorship program for first time speakers is planned as well. - Sponsorship packages are already available for review. If you decide to sponsor until May 7, you can get a 10% Early Bird discount on your packages. We will send out more detailed posts on the above items in due course. Please subscribe to our newsletter if you want to make sure to get all information: https://ep2021.europython.eu/newsletter/ Help spread the word Please help us spread this message by sharing it on your social networks as widely as possible. Thank you ! Link to the blog post: https://blog.europython.eu/europython-2021-launching-the-conference-website/ Tweet: https://twitter.com/europython/status/1382986951830204420 Enjoy, -- EuroPython 2021 Team https://www.europython-society.org/ -- https://mail.python.org/mailman/listinfo/python-list
Re: TIME IN XARRAY
On 15/04/2021 20:20, Chris Angelico wrote:
On Fri, Apr 16, 2021 at 4:16 AM Jorge Conforte wrote:
I'm using xarray to read netcdf data and I had to time in my data the
values:
xarray.DataArray 'time' (time: 507)>
array(['1979-01-01T00:00:00.0', '1979-02-01T00:00:00.0',
'1979-03-01T00:00:00.0', ...,
'2021-01-01T00:00:00.0',
'2021-02-01T00:00:00.0', '2021-03-01T00:00:00.0'],
dtype='datetime64[ns]')
Please, how can I get the years and months values from this array.
Looks like your "time" values are ISO-8601 dates, stored as strings.
You should be able to parse them easily by hand, or hand them to
datetime.datetime.fromisoformat().
The dtype is a strong hint that there is a numpy or pandas datetime
object underneath the misleading repr().
Assuming that x is the column array I'd try
[d.year for d in x]
or
x.map(operator.attrgetter("year"))
--
https://mail.python.org/mailman/listinfo/python-list
Re: Repair Install of 64 bit python
Isn't the recommended python3 way of pip-ing stuff: python3 -m pip install ... .. just curious. On Thu, Apr 15, 2021 at 08:36:56PM -0500, o1bigtenor wrote: On Thu, Apr 15, 2021 at 8:03 PM Dodson, Matthew wrote: Hi, Having an issue after installing 64 bit python. Can't pip install any packages. Get the error "No module named pip". No expert here but to me that reads like you need to install 'pip'. On linux I need to make sure its pip3 - - - for python 3. Then after that's done you sounds be able to go $ pip3 install x . HTH -- https://mail.python.org/mailman/listinfo/python-list -- Daniel Ciprus .:|:.:|:. CONSULTING ENGINEER.CUSTOMER DELIVERY Cisco Systems Inc. dcip...@cisco.com tel: +1-703-484-0205 mob: +1-540-223-7098 signature.asc Description: PGP signature -- https://mail.python.org/mailman/listinfo/python-list
Re: Repair Install of 64 bit python
On 16Apr2021 13:13, Dan Ciprus (dciprus) wrote: >Isn't the recommended python3 way of pip-ing stuff: > >python3 -m pip install ... > >.. just curious. If there's only one Python 3 installed then "pip3 install ..." _ought_ to be equivalent. However, in the face of virtualenvs etc there may often be several pip3s. Using "python3 -m pip install ..." ensures that you are using the pip which is associated with "python3" (which you can adjust to be whichever python3 you intend). This is why the "-m pip" form is recommended: it definitely installs in the Python you'd be running. Cheers, Cameron Simpson -- https://mail.python.org/mailman/listinfo/python-list
Async telnet, which package and how?
Hi, I have to asynchronously connect to many home routers with telnet protocol in order to get some values. Upon getting input data (ip, username, password), I should connect to the router, execute commands, get their results, postprocess results and finally return certain values. Everything should work in asyncio loop. I searched a bit and I found that people usually use telnetlib3 for such task, but I can't find out examples that shows how to use telnetlib3.TelnetClient for my use case. If someone here has some experiences or has some demo code, please share. Regards. -- https://mail.python.org/mailman/listinfo/python-list
setting user input equal to target language in Google Translator
is it possible to set the target language of a translation to be the input from a user? I have tried inputting specific abbreviations that would normally be accepted as the target language but it remains in Icelandic and I would like to change the target language based on the user's input without creating hundred of scenarios for each inputted language or country. Thanks -- https://mail.python.org/mailman/listinfo/python-list
Re: port to PDOS (especially mainframe)
On Wednesday, April 14, 2021 at 8:35:59 PM UTC+10, Paul Edwards wrote:
> ImportError: importlib requires posix or nt
> but I don't know what it needs to satisfy that.
>
> It's a bit strange that it can only be posix or nt when VMS is supported in
> 3.3 too.
The resolution to this problem was to include:
{"posix", PyInit_posix},
in config.c
and compile posixmodule.c.
I'm now on to the next problem.
BFN. Paul.
--
https://mail.python.org/mailman/listinfo/python-list
Re: setting user input equal to target language in Google Translator
On 16/04/2021 19:11, Quentin Bock wrote:
is it possible to set the target language of a translation to be the input
from a user?
I have tried inputting specific abbreviations that would normally be
accepted as the target language but it remains in Icelandic and I would
like to change the target language based on the user's input without
creating hundred of scenarios for each inputted language or country.
Thanks
Hi, Quentin!
When you ask a question it is best to give the code you have. For
beginner problems you may even get a hint from people who haven't used
the library in question. That said, I have just installed googletrans,
and changing the destination language appears to be as easy as
>>> import googletrans as gt
>>> t = gt.Translator()
>>> for language in ["de", "fr", "es"]:
... print(t.translate("Hello, world!", dest=language).text)
...
Hallo Welt!
Bonjour le monde!
¡Hola Mundo!
Does that help?
--
https://mail.python.org/mailman/listinfo/python-list
Re: port to PDOS (especially mainframe)
On Saturday, April 17, 2021 at 5:13:31 AM UTC+10, Paul Rubin wrote: > Paul Edwards writes: > > I have succeeded in producing a Python 3.3 executable despite being > > built with a C library that only supports C90. > It seems to me that you might have an easier time porting MicroPython > than CPython, if MicroPython fills your requirements. The documentation for "asma" says it requires Python 3.3 or above, and I have no idea how accurate that claim is. I'll only know whether *my* flavor of Python 3.3 is good enough for "asma" when I reach that point. BFN. Paul. -- https://mail.python.org/mailman/listinfo/python-list
Re: port to PDOS (especially mainframe)
On Fri, Apr 16, 2021 at 1:05 PM Paul Edwards wrote: > On Saturday, April 17, 2021 at 5:13:31 AM UTC+10, Paul Rubin wrote: > > Paul Edwards writes: > > > I have succeeded in producing a Python 3.3 executable despite being > > > built with a C library that only supports C90. > > > It seems to me that you might have an easier time porting MicroPython > > than CPython, if MicroPython fills your requirements. > > The documentation for "asma" says it requires Python 3.3 > or above, and I have no idea how accurate that claim is. > > I'll only know whether *my* flavor of Python 3.3 is good > enough for "asma" when I reach that point. > It'd probably be pretty simple to build micropython on a Linux system, and try to run asma on that. I've built micropython Linux before. If asma runs there, it'd suggest you might do well to port micropython to PDOS instead. Micropython has the dual benefits of being small and being supported. CPython 3.3 doesn't even get security fixes anymore. -- https://mail.python.org/mailman/listinfo/python-list
Re: port to PDOS (especially mainframe)
On Saturday, April 17, 2021 at 6:18:29 AM UTC+10, Dan Stromberg wrote: > If asma runs there, it'd suggest you might do well to port micropython to > PDOS instead. > > Micropython has the dual benefits of being small and being supported. > CPython 3.3 doesn't even get security fixes anymore. Ok, thanks. I'll consider doing that as well. BFN. Paul. -- https://mail.python.org/mailman/listinfo/python-list
Re: port to PDOS (especially mainframe)
Il 23/03/2021 10:23, Paul Edwards ha scritto: Hello. I have a new operating system called PDOS which works on both PC and mainframe, which can be found here: http://pdos.sourceforge.net/ I know nothing about Python, my focus is on C90, but I wish to run this mainframe assembler, asma, which was written in Python, not C: https://github.com/s390guy/SATK It needs Python 3.3 as a minimum, so I wish to port that version, first to the PC version of PDOS, then to the mainframe version. I don't wish to run configure, I want to hand-construct the makefile. PDOS is a very simple system, so I only want to produce a single executable, no DLLs etc. I don't need extensions to work or anything, all I need to be able to do is run asma. I've started constructing a makefile (see below), which I execute with pdmake, included in PDOS. I only have a C90 runtime library, no more, no less, so I don't know whether Python will actually build in my environment, but so far things have been building successfully. However I'm currently stuck on this unresolved external: python.a(abstract.o)(.text+0x668c):abstract.c: undefined reference to `PyExc_StopIteration' What source file is meant to define that variable (PyExc_StopIteration) as opposed to just declaring it or using it? I tried looking at the OS/2 EMX for hints, but wasn't able to figure it out. Note that I am building a Win32 executable to start with, but it is linking against my own C90 library which will call either Microsoft's MSVCRT.DLL on Windows, or my own MSVCRT.DLL when running on PDOS/386 (aka PD-Windows). I also don't know whether Python will survive being transferred to an EBCDIC environment, as that is where it will ultimately need to be compiled and linked (MVS/380), or at least assembled, before it can wind up on PDOS/3X0. Well, maybe it can all be done on Windows. I need to see what asma is capable of. Thanks. Paul. # Produce Windows executables # links with PDPCLIB created by makefile.msv CC=gccwin CFLAGS=-O0 LD=ldwin LDFLAGS= AS=aswin AR=arwin STRIP=stripwin COPTS=-S $(CFLAGS) -fno-common -ansi -I. -I../Include -I../../pdos/pdpclib -D__WIN32__ all: clean python.exe python.exe: python.o ../Python/strdup.o ../Objects/object.o ../Objects/abstract.o \ ../Python/errors.o ../Objects/bytesobject.o rm -f python.a ar r python.a ../Python/strdup.o ../Objects/object.o ../Objects/abstract.o ar r python.a ../Python/errors.o ../Objects/bytesobject.o $(LD) $(LDFLAGS) -o python.exe ../../pdos/pdpclib/w32start.o python.o python.a ../../pdos/pdpclib/msvcrt.a ../../pdos/src/kernel32.a $(STRIP) python.exe .c.o: $(CC) $(COPTS) -o $*.s $< $(AS) -o $@ $*.s rm -f $*.s clean: rm -f *.o python.exe Hi, one thing is not clear to me, do you absolutely need to use "asma"? http://www.z390.org/ -- https://mail.python.org/mailman/listinfo/python-list
Re: port to PDOS (especially mainframe)
On Saturday, April 17, 2021 at 7:52:07 AM UTC+10, jak wrote: > Hi, > one thing is not clear to me, do you absolutely need to use "asma"? > > http://www.z390.org/ The link you provided is to something that runs on PC environments. I want to produce EBCDIC executables that run on a S/3X0 (or z/Arch) machine (even if I personally do that via emulation). The only way I currently have of doing that is to assemble and link using what comes with MVS 3.8J. But that's all written in S/370 assembler using features that only exist on MVS. PDOS/3X0 doesn't support all those features. It only supports C90-compliant applications. Meanwhile, 35,000 lines (or more) of lovingly handcrafted Python code are going to waste. :-) BFN. Paul. -- https://mail.python.org/mailman/listinfo/python-list
Re: port to PDOS (especially mainframe)
On Fri, Apr 16, 2021 at 3:40 PM Paul Edwards wrote: > On Saturday, April 17, 2021 at 7:52:07 AM UTC+10, jak wrote: > > > Hi, > > one thing is not clear to me, do you absolutely need to use "asma"? > > > > http://www.z390.org/ > > The link you provided is to something that runs on PC > environments. > > I want to produce EBCDIC executables that run on a > S/3X0 (or z/Arch) machine (even if I personally do > that via emulation). > I thought EBCDIC was analogous to ASCII? Is it also analogous to a.out, ELF and COFF? -- https://mail.python.org/mailman/listinfo/python-list
